There are many ways to expend the knowledge as a QA:
Read QA blogs.
Read Testing books.
Hone your QA skills by teaching others.
Go to Meet-Up & grow your network.
Search & Read the Research Papers.
Go to the Conference & Company Seminar.
One of the best ways to learn Ask Q/A on Stack Exchange sites.
Work on Open Source /Crowd Testing Projects. (...
There are several tools for the AI Driven Testing (AI-DT). here is the list of few tool they have some trial version period but not sure about the open source.
I think your suggestions are very good, it is always good to have clear guidelines. Though they should not be set in stone and should be used as a guideline and not as a rule.
In order to reproduce the issue I want as much information as possible. A screenshot can tell a thousand words. Some people make only a screenshot of the part they think ...
First of all, I doubt that there is currently something like AI-driven testing. *-driven means that your entire development/testing process strongly relies on *. Working for retest myself, I'm convinced—due to my experience there—that AI can be a great help to complement traditional testing approaches. But: Today's AI is inferior to hand-crafted test scripts ...
I'd suggest you start with the software quality blogs and forums around the Internet. Some of the online portals I like are:
Joe Strazzere's All Things Quality
The Software Testing Club portal (they have a pretty good forum, too)
The Ministry of Testing portal (their listing of tools is long and could use more detail, but has a lot of information condensed ...
Yes, that would be awesome, but there is no such tool. (If you are very ambitious, you can try writing it yourself.)
The reality of cross-platform UI automation is that it is brittle and requires a lot of maintenance. Any vendor who claims otherwise is more interested in taking your money than solving your problems.
Here are some alternatives:
In this context, a goal you most likely want to achieve is one of Continuous Integration (CI).
To that end, from the developer side, every check-in will trigger a build (to perform certain checks and see if it passes). Then you will usually have a nightly build that gives you an up-to-date test environment every morning.
Now, this pipeline should include ...
I can suggest you Appium is the best tool for Android & iOS mobile testing.
I'm working on appium from last 6 months in my organization.
The main advantages of using Appium is:
Backend is Selenium so you will get all selenium functionality
Able to test iOS and Android
Continuous integration support
Doesn't require access to your source ...
One more important thing people forget communication tools, a tester should always ask questions, so we need some communication tools like Hipchat, Skype, slack, whatsapp...etc or any client email tool.
Clipboard Manager is very useful tool for multiple copy history.
There are no tools that can provide you client-side rendering times. Client side rendering is not a measurable value, unless all of the devices accessing the system are identical in terms of hardware and network access to the SUT.
However, It is completely viable to do a stopwatch test of the total page rendering time, as long as you communicate to the ...
I think you want to pick the framework which has the most active development and the most documentation resources on the internet.
Of-course you first need to check which framework fits your requirements, I would pilot all for a short while (starting with the most active one. If you have multiple candidates.)
Which is more popular:
Number of (recent) ...
I find MITM proxies and Mocks/Stubbing to be the most advanced pieces of Technology in Automated Checking.
By using these, it makes it far easier to:
Create repeatable, consistent checks
Decrease overall execution speed
Segregate the application into logical pieces
Record executed manual tests
But for the real answer, QA's knowledge and senses is the most ...
Test open source software and report defects on Github. Maybe start with the top open source applications, you might already be using some.
Try to answers questions here on SQA.SE. If you cannot answer them do research (and create a proof of concept) until you can. This helped me greatly.
Read testing blogs
Read testing books
My personal opinion is that ...
The platform that need to be supported are:
iOS, Android, Windows Mobile, Windows Phone
— For your needs you can use SeeTest, EggPlant, Ranorex, Borland Silk Mobile — but they all are commercial solutions, most have free trial.
SeeTest is quite popular at the moment and has very positive feedback. Another good one is EggPlant as I know.
I have always loved using Scooter Software - Beyond Compare (limited to 2 links) to visually compare between folder, files etc. Group of them or single.
This should help with an easy to use Visual Compare.
Daniel has created a great BC File Extension Forum Link | How To on GitHub.
It uses simple export with command line to do compare SQLite DB.
I came across XRAY on Jira Cloud and i found its really usefull, I have started using in our company and replaced zephyr . Xray will give the opportunity to maintain both manual and automated test in one single interface. It support Rest api so you can import results from jenkins and update jira issues also.
For some performance testing you don't need a specific tool, only a well-designed test case set, a bunch of test suites which with some variables can be used on any type of operating system family.
When you design the test cases, you should take in consideration the application's requirements and non-functionalities:
how many users will use the ...
For really good, robust, maintainable UI automated regression, you need code. Using screenshots is bad for several reasons:
Even with a fuzz tolerance built in to prevent things like the exact color of the display throwing false positives, there are too many trivial things that can throw a false positive.
A change of display resolution will utterly destroy ...
We have spent a couple of days to try and test the Atlassian way of running tests in Jira from their confluence pages. After evaluation of others tools we decided to use a commercial tool that integrated with Jira.
Create new Testcase issue type (with custom fields and status Passed/Failed)
Create subtask of the issue (add version)
Install Google chrome.
Install Blazemeter extension in chrome.
Download JMeter and set it up. Lots of tutorials available for that.
Record scripts with blazemeter and download them.
Run the scripts in JMeter.
If we define corrupt as not being able to start the executable, just open it with a text editor (like notepad++) and change some text around and save. Some executables might be to large to open, but I think a good text-editor should be able to handle most. Open the executable, if it still works, change more text around :)
The smallest changes will often ...
Images for bug reports should:
contain all the information needed. So for browser screenshots use the whole browser window so people can see the browser, browser version and any toolbars that reflect installed tools and any footer toolbars that show info.
not contain irrelevant information. I am not a fan of the whole desktop screenshot as it includes too ...
I will answer/go through your points one by one and will try to add some valuable information in addition to your useful & precised description.
Color usage in images: Highlighting becomes critically important when creating bugs related to GUI. Regarding the color, we have been using Red (R =255, G=B=0) and Blue (R=G=0, B=255) color only for ...
The most recent developments that I have observed are:
Running tests in the cloud. Companies like Sauce Labs and Browserstack are leaders here. There are many advantages to this, from the number of devices being tested to the number of parallels servers that can be used.
Writing UI tests using UI tools. Products such as Ghostinspector, heliumhq and ...
I use following tool with my team: SBTM template for google spreadsheet from Altom (altom.ro)- https://drive.google.com/templates?q=SBTM+Session+Template&sort=hottest&view=public.
It is spreadsheet running on google spreadsheets platform boosted with google apps script.
For me it's adding lot of value as it:
Is easy to use and has lot of ...
All tools I know for iOS apps testing are:
Apple Instruments (UIAutomation)
These two use Selenium / WebDriver API and support many languages. Appium is multi-platform, faster developed and supported, has more users. Easy ...
A reply equally broad as the question, but that does answer it:
Go to https://www.testtoolreview.de
Filter tools based on your specific situation
Compare the available options on specifications that matter to you
Pick a winner
You should research a bit more before asking generic questions like that.
Jira is a very flexible tool. You can use it as a workflow management tool for managing any software life-cycle.
It does not really need to know any knowledge of what kind of application you are developing. You can define any number of custom fields and or workflow steps you might need to differentiate between platform and or workflows.
I have used Jira ...