Verification Testing – confirming you built the system right
Verification is what most people think of when they hear the word testing – it is the process of testing whether a solution does what it is designed to do.
During verification, the testing team which may consist of developers, quality assurance people, and some business analyst’s, put the software or system so it’s places to confirm that it operates as expected and ensure that it conforms to the design specifications laid out earlier within the project.
Verification testing includes four phases:
- One pretest phase
- three phases of actual testing
Each phrase has its own objective, participants, activities, and deliverables
Understanding the phases and the language that surround this activity how to communicate effectively with those performing the testing, so I will break down the component tests in the rest of this article.
This test will not be hazardous to your health! A smoke test is also called a build verification test, and as a pretest that determines whether for testing and even begin in the first place.
A smoke test reveals any simple failures in the solution that may prevent you from executing the tests in the next three phrases. Some project teams made link this test to unit testing, which I will explain in a minute.
The testing team can conduct a smoke test, using automated or manual tools.
The unit test is the first actual phase of testing and involves testing each unit (a small piece of code or part of a system that can be independently compiled, such as an individual programme or module). This unit test of the system is done as a standalone test.
An example of the unit is shown in the diagram below as “Place Order”:
The development team generally performs line by line testing of both function and structure to find bugs within the unit before any other tests are done.
Although unit tests are performed by the development team, you should have another group other than the development team, test to ensure unbiased testing.
The second phase of testing, integration tests, ensures the individual units are working together. These individual units working together can be considered a subsystem, a piece of the overall system, or just linked units.
The objective of this test is to find problems with how the components of the system work together, and it test the validity of the software architecture design.
The development team generally performs the integration tests, although assurance or business analyst’s may help by providing test cases and reviewing test results.
Keep the following in mind about integration testing:
Units are not included in integration testing until may have successfully passed unit testing
Sometimes integration tests can have multiple levels of integration
Multiple levels mean sometimes several subsystems brought together and tested and then those subsystems integrated with larger subsystems.
This test make sure the software installs on the machine as you expect it to with no problems in the installation process. When testing, make sure the requirements for the system you are installing are clearly stated.
This test determines how well the product works with different environmental configurations. As an example, if your requirement states the product requires a hardware model with a specific version of software installed, you need to test installation with other operating systems and other considerations of hardware.
In fact, you see configuration or time on a product’s system requirements. When a software manufacturer advertises its product as working with that configuration, you can believe the company has gone through configuration tests to ensure the product meets so specifications.
A usability test is really a validation test; however, it is sometimes done during system test time, depending on the visibility of the solution.
If it is a website that millions of customers will use or see, chances are you want to bring in usability engineers to build in usability instead of to waiting to test it at the end of the project.
Although your project may not be a multimillion dollar release, you still need to ensure that users will be able to effectively use it