Testing

As we seen in the Waterfall model the issues found in the end of the SDLC, this is due to the testing is occurred in the end phases of the you SDLC. To overcome this problem the V-Model is comes into the picture. It is always better to introduce testing in the early phase of SDLC,

In this method of testing the testcases are calculated based on analysis internal structure of the system based on Code coverage, branches coverage, paths coverage, condition Coverage etc.

Typically such method are used at Unit Testing of the code but this different as Unit testing done by the developer & White Box Testing done by the testers.

The White-box testing is one of the best method to find out the errors in the software application in early stage of software development life cycle.

 all available functions are executed to complete 100% code coverage of testing.

Black Box Testing 

we are treating this as black box & without checking internal structure of software we test the software. All testing is done as customer’s point of view and tester is only aware of what is software is suppose to do but how these requests are processing by software is not aware.

The main purpose of the Black Box is to check whether the software is working as per expected in requirement document for Validation purpose.

Types of Black Box Testing Techniques: Following black box testing techniques are used for testing the software application.

• Boundary Value Analysis (BVA)
• Memory and platform related
• Decision Table based testing
• Cause-Effect Graphing Technique
• Error Guessing 

Smoke Testing and sanity testing

‘Smoke Testing’ is came from the hardware testing, in the hardware testing initial pass is done to check if it did not catch the fire or smoked in the initial switch on.

The Smoke testing is typically executed by testers after every build is received for checking the build is in testable condition. This type of testing is applicable in the Integration Testing, System Testing and Acceptance Testing levels.

Sanity Testing

After receiving a Software build with the minor issues fixes in code or functionality, Sanity testing is carry out to check whether the bugs reported in previous build are fixed & there is regression introduced due to these fixes i.e. not breaking any previously working functionality.

Regression testing is type of testing carried out to ensure that changes made in the fixes or any enhancement changes are not impacting the previously working functionality. It is executed after enhancement or defect fixes in the software or its environment.

The automated testing methods are the best and safe option to carry out the Regression testing.