Manual Testing: Types and Steps to Reproduce

Posted on

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

As we live in the age of agile methodology, testers and developers should learn to work cooperatively. Thus, the test process execution depends on software development life cycle (SDLC) too.

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

How to Implement Manual Testing in the Context of SDLC?

  • Documentation – the stage of requirement gathering where business analyst creates documentation.
  • Discussion – the process of sharing requirements with other interested people: developers, testers, and so on. It is usually performed in the form of meeting.
  • Designing – after all requirements are considered, the dev team proceeds to design the system architecture. This may include selecting the dev approach, flow charts, creating a design document, and etc.
  • Creating test cases – while development team is coding, the test team is writing test scenarios which as time passed are transformed into test cases for checking the developed system. Ideally, the testers should show their test scenarios with the developers.
  • Coding – it is time for the dev team to start the development process. This stage should obligatory contain unit testing. Also, the testers like to execute white-box testing at this phase before proceeding directly to the full testing.
  • Testing – undoubtedly, the time of starting this stage varies from company to company, developing on the peculiarities of the specified project. The testers run the earlier prepared test cases, open bugs, assign them to the developers, execute regression testing, and many other activities.
  • Review – this is the last obligatory stage with which any project is ended; business analyst checks the developed and thoroughly tested functionality, based on the results, reports, and his own actual experience.

When all the above-mentioned steps are taken and business analyst submit a good feedback the project may go into the phase of release.

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

The 6th stage of development process may include several dozens of testing types. We would like to introduce the most important ones.

The Most Common Types of Manual Testing:

  • functional testing – checking the system functionality;
  • usability testing – checking how users understand the system logic and are satisfied with it;
  • security control – the testers usually perform SQL injection, cross-site scripting, URL tampering, and other procedures in order to test data security;
  • performance testing – checking the response time of application;
  • multi-platform testing – checking the app functionality over most popular platforms and browsers.

Leave a Reply

Your email address will not be published. Required fields are marked *