How to effectively manage manual tests in a project?

Question

In our team, we encountered the problem of manual testing. We have a set of unit tests that maintain a stable project, but we also periodically check our application manually based on some scenarios (to check if everything is in order at the highest level).

Question: How to effectively manage manual test scripts? They may change from time to time as changes are made to the application. Is there any other way to update text files or wikis? How to track, someone did some kind of test and what were the results?

Do you know the tools addressed to this problem (test case management)?

Answer 1

Well, of course, there are tools.

Recently, we had a presentation of MS Test Manager, although I know about other tools (Quality Center, Doors, etc. .... and even some Open Source).

http://www.opensourcetesting.org/testmgt.php

We actually manage them with EXCEL sheets, but as our number of manual test cases is constantly growing, we plan to start using a testing management tool.

Answer 2

Our organization uses MS Test Professional. This tool not only allows you to manage your test cases manually, but also gives you a list of recommended tests based on code changes in the assembly under test. Test Professional will also allow you to look back into the past of test cases that contain the results of individual tests. Here is a link to the Test Professional FAQ .

Answer 3

Tracking the work of team members is pretty straight forward using Jira. I have used it in the past and you cannot beat it for the price (i.e. for free!)

Script management is a little tougher. Most companies struggle with this at a certain level. Especially when they start to increase. I heard that the Telerik test studio can be useful.

Answer 4

We use the Jira management tool. This tool will help you with development testing and .

Using this tool, you can record test cases, as well as manage all test scenarios (whether the test is skipped, failed or invalid). If you want, you can raise a bug in the dir itself, and you can associate the Testcase ID with the bug so developers can change functionality on demand.

Answer 5

There is a Testlink tool. This is open source written in php and you can make the changes yourself. In Testlink, you collect test cases and test scripts, and then create test plans. And these test plans are for a specific version of the tested system. Thus, you can collect several versions of test cases that correspond to the versions of the system. In this tool, you also mark the results of the test cases that you performed. You can also integrate it to release the management tool, and you can create problems directly from Testlink.

Answer 6

I think the best way to manage manual testing is:

• Identify test cases that are important for the module / project.
  • Try checking it manually.
  • We call these scripts smoke test.
• Determine where auto-intervention fails.
  • Not everything within the module / project is automated.
  • These are cases that will help you easily test manually.