Any software testing company has its own testing model, and testers try to follow it precisely. However, there is another important factor: the stage of development.

As we live in the age of agile, testers and developers must learn to work cooperatively. Therefore, the execution of the testing process also depends on the software development life cycle (SDLC).

Let’s try to consider manual testing implementation in terms of development stages and agile environment.

How to implement manual tests in the context of SDLC?

  • Documentation – The requirements gathering stage in which the business analyst creates the documentation.

  • Discussion: The process of sharing requirements with other interested people: developers, testers, etc. It is usually done in the form of a meeting.

  • Design: After considering all the requirements, the development team proceeds to design the architecture of the system. This may include selecting the development approach, flowcharting, creating a design document, etc.

  • Creation of test cases: While the development team codes, the test team writes test scenarios that, over time, are transformed into test cases to verify the developed system. Ideally, testers should show their test scenarios to developers.

  • Coding: It’s time for the development team to start the development process. This stage should contain unit tests. Also, testers like to run white box tests in this phase before proceeding directly to full testing.

  • Testing: Undoubtedly, the time to start this stage varies from one company to another, developing on the peculiarities of the specified project. Testers run the previously prepared test cases, open bugs, assign them to developers, run regression tests, and many other activities.

  • Review: this is the last mandatory stage with which any project ends; The business analyst verifies the developed and thoroughly tested functionality, based on the results, reports and his own actual experience.

When all the steps mentioned above are taken and good feedback is provided by the business analyst, the project can move to the launch phase.

Sometimes testers may perform sanity testing or pre-release testing even after the analyst has already obtained a positive overview of the software product.

The sixth stage of the development process can include several dozen test types. We would like to present the most important ones.

The most common types of manual tests:

  • functional tests: verification of the functionality of the system;

  • usability testing: checking how users understand the logic of the system and are satisfied with it;

  • Security check: Testers typically perform SQL injection, cross-site scripting, URL manipulation, and other procedures to test data security;

  • performance tests: verification of the application response time;

  • Cross-platform testing: verification of the application’s functionality on the most popular platforms and browsers.