SQA Careers   |   SQA Adepts   |   SQA forums   |   SQA Blogs   |    SQA Discussion Boards   |   SQA Links
Web VAssure.com
Our Products
Home > Services > Testing Labs > White Box Testing
White Box Testing

White-box testing not only verifies that the basic unit of code (class/ function/ procedure) behaves properly when appropriate input is given but also validates that unexpected inputs do not cause application crashes.

White-box testing enables the process of testing that is seamlessly integrated with the process of development, resulting in the reduction of overall development time and effort. This testing methodology helps in decreasing cascading errors, reduces test-time in future releases and minimizes the development and maintenance time for the code.

Our approach ensures proper design of the tests and the identification of all the mandatory test inputs to reap all the advantages of White-box testing. We proceed with creating test plans drawn up using use cases. After the developers review test plans, we design test procedures, including input data. We then proceed based on these test procedures and report the results to the development team.

Quality support at this stage includes, code verification via walk-throughs, checking for coding and algorithmic standards, traceability of code to low-level design documentation and follow up on suggestions/comments from developers as well as testers.

Prudent steps we take in designing white box test cases are :

The major steps in White Box testing by VAssure are :

Equivalence/class boundary analysis
Basis Set
We look for metric for accessing how good is our test case is:

• method coverage
• Statement coverage
• Decision coverage
• Branch coverage
• Condition coverage

We think diabolically while generating the required test cases.
Exhaustive testing: run every possible code coverage and functional execution.
Unit testing: construct tests directly from the code reviews and High/Low level design document

VAssure's team derives test cases for White box testing such that:

Guarantee all independent paths in a module have have been tested (exercised) at least once.
Exercise all logical decisions or both true an false conditions.
Execute all loops at their boundary values and within their operational bounds.
Exercise internal data structures to ensure their validity.

Home | Company | Services | Engagement Model | Infrastructure | Insight | SQA Careers | SQA Adepts | Site Map | Contact us
Privacy Policy | Terms & Conditions | Disclaimer