VerifyQA Manual Testing
VerifyQA provides manual testing services to manually test software for defects. It requires a tester to play the role of an end user, and use most of all features of the application to ensure correct behavior. To ensure completeness of testing, the tester often follows a written test plan that leads them through a set of important test cases.
Our Manual Testing Includes
- Adherence to different Software models as per the need of the projects which mostly includes Agile Model.
- Strong adherence to STLC starting at project analysis, passes through test cases creation and ends at final report having been through test execution & at least three rounds of testing.
- Strong adherence to Test case matrix where each and every requirement is mapped with test cases created.
- Excellent tracking of bugs with the help of Eventum Bug Tracker.
- Excellent maintenance of Test Repository with the help of Testlink.
- Strong emphasis on Core Functionality Test, Usability Test, Data type Test, Browser Or Device
Our Manual Testing Stages
This initial stage in testing is normally carried out by the developer who writes the code and sometimes by a peer using the white box testing technique.
This stage is carried out in two modes, as a complete package or as an increment to the earlier package. Most of the time black box testing technique is used. However, sometimes a combination of Black and White box testing is also used in this stage.
After the integration has been tested, software testers who may be a manual tester or automated perform software testing on complete software build. This Software testing consists of two type of testing - Functional and Non-Functional Testing.
Release or Deployment Testing
If required onsite team visits customer site to install the system in customer configured environment and will check for the following points:
- Whether SetUp.exe is running or not.
- There are easy screens during installation
- How much space is occupied by system on HDD
- Is the system completely uninstalled when opted to uninstall from the system.
In this stage the software is tested from all possible dimensions for all intended purposes and platforms. In this stage Black box testing technique is normally used.
User Acceptance Testing
This testing stage carried out in order to get customer sign-off of finished product. A 'pass' in this stage also ensures that the customer has accepted the software and is ready for their use.