Manual testing tool recommendations

Hey there, I’m a freelance developer and a client of mine is looking for a tool for QA testing for their mobile app. They have a couple of automated tests (i.e. unit tests) but most of their QA is manual and they use a Google Doc and Excel sheet to track the different test cases.

Which tool do you use for manual testing?


It depends on what I’m testing but I do have a few favourite tools I use daily!

Hope this helps :slight_smile:


Thanks @james_qa, I didn’t know Wave and screencast-o-matic!
But what I’m looking for is something to organize the manual test suite better – not sure I’m using the proper terms though :sweat_smile:

I have used TestRail in the past. Integrates with Jira quite well, too, if you are using that.

TestRail is geared towards regression testing but you can create one-off suites as well.

Thanks @froberts! Yes, I had a look at Testrail but it doesn’t seem to be so intuitive. At least for me, not knowing so much about the QA terms and processes.

I do manual regression testing where I work and we use Testrail. When I first started working here, they had test cases in TFS(Azure) and I had to export them and import them into testrail (not a fun process). Our Scrum Team QAs/functional testers use Azure for their test cases. TFS has some cool options for integrating with the builds, etc., but it is definitely not ideal for regression.

TestRail is definitely designed more for Regression testing. To start, Testrail, has two, organization structures, i.e., repository types ypu can choose from, single repository and multiple repository. This is where the organization of it comes into play. Ours was set us as multiple repository when I started working here. It consists of test suites. What i found was that when i created test runs, it was less than smooth to add specific test cases and/or entire groups of test cases to the test runs.

So I changed to the default recommended single repository which has sections and sub sections instead of testsuites. It works so much better.

Basically, what I do is I confirm with upper management which areas and functions of the software are priority using priority 1- priority 4.

We have monthly releases. So each month, I create a Milestone in Testrail for that months release. Then I create a Test Run within that Milestone containing the priority tests divided by Priority. Then as we are testing during the 2 week regression cycle testrail will give you a visual chart showing progress of each run, including ran, not ran, passed, failed, ect. What I like best about testrail is that you can drag and drop the test cases into other folders, you can bulk edit specific data on the test cases at once like priority, etc.

Also, when I first started using it, I created 3 different projects because I started over a couple of times and wanted to see how it would flow with different setups. One other thing is if you edit a test case that is actively in a test run, it will update the test case that is in the run as well, which is nice.

Theres also a plethora of reporting that can be done and can be emailed to you or to a group of people and can be scheduled to regularly be sent.

Hope this helps some!


Thanks for the very complete answer @tech4ever1! :pray:

When you say “its not intuitive”, what might you be looking for? I will also recommend HP ALM, and Ranorex if you have not checked them out.


Most of the manual testers used these below tools while doing manual testing.

1.Test Case Management Tools (TCMT) and
2.Defect Tracking Tools (DTT)

There are various Test Case Management Tools are available but mainly I refer Test Manager, Test link, Spira, TCZILLA, Test Rail, QC etc.

Defect tracking tools are mainly used to track the defects which are found in the application
if you want to know more about this please check here: Top Defects/ Bug Tracking Tools

I hope it is helpful for you…
Keep Reading

Correcting the use of ‘manual testing’ is not just about game on words, BUT an act of respect to testers and testing.

:point_right: Use #Testing when you mean testing.

:point_right: Use #AutomationInTesting when you mean the use of automation to assist testing.

:point_right: Use #Checking when you mean checking.

Think about it before you prefix #testers or #testing with #manual next time.


I will suggest you to use, where most of the manual testers used while doing manual testing.

I hope it is helpful

Worth looking from @testertested

I would recommend two articles to start with

This article explains why “manual testing” is not the correct term to use in testing :point_down:


this article explains why testers should not put too much focus on tracking test cases. there are more important stuff to do in testing - ‘the thinking’ ‘new test ideas’

you can use some mindmap tools to visualise your test ideas but please do not track and then report on the numbers to anyone as “testing progress report” or similar

I meant for someone like me who’s not so knowledgeable in QA jargon, it doesn’t feel easy to setup for the simple use case of my client.

Thanks @priti_testrig, that’s definitely helpful! I know now that what they’re looking for is more of a TCMT, since they use GitHub to track all the bugs.

Thanks @testerawesome for pointing that. And I didn’t mean to offend but as I said in another response I’m not accustomed with the QA jargon, now I am and I’ll pay attention in the future :pray:

1 Like

Thank you for your understanding and I appreciate your attitude on this.

I’m one the a few amongst testers encourage others to use the appropriate terms.

Manual prefix is more likely invented to accommodate the automation works in testing. (Personally, I think it’s wrong.)

It should be the other way around. Automation is here to assist and accommodate human activities.

Thank you again for your understanding. I hope blog posts or articles I shared above gives you some new perspective of thinking how you may tackle your current problem.

1 Like

@jeremybenaim We use JIRA for requirements and development workflow management. The JIRA Xray plugin is also used to manage all our test cases.

There is many test case management plugins for JIRA.


The essential tool we all bring to our testing problems is the Mk.1 Brain.

1 Like

We use Azure DevOps for requirements and workflow (and also document the testing of each work item). Manual regression test scripts are recorded in word and excel (the testing itself is tasked in Azure DevOps) but most important tool for manual testing is the tester. No process will give a good test coverage unless you’ve got a fantastic team of testers with inquiring minds.