Search

Tuesday, June 03, 2008

The V-Concept of Testing

The V Concept of testing detail on the sequence with which the testing should be performed. The life cycle testing is performed against the deliverables at the pre-determined specified points. The SDLC has to be pre-determined for this to happen.
The V concept recommends both the System Development and the System test process to start at the same point referring the same information. The development will have the responsibility of documenting the requirements for the development purpose; which the test team could use for testing purpose as well.In the V-testing concept, your project’s Do and Check procedures slowly converge from start to finish, which indicates that as the Do team attempts to implement a solution, the Check team concurrently develops a process to minimize or eliminate the risk. If the two groups work closely together, the high level of risk at a project’s inception will decrease to an acceptable level by the project’s conclusion.

The various steps involved in V-concept are listed below:

Step 1: Assess Development Plan and StatusThis first step is a prerequisite to building the VV&T Plan used to evaluate the implemented software solution. During this step, testers challenge the completeness and correctness of the development plan. Based on the extensiveness and completeness of the Project Plan the testers can estimate the amount of resources they will need to test the implemented software solution.Step 2: Develop the Test PlanForming the plan for testing will follow the same pattern as any software planning process. The structure of all plans should be the same, but the content will vary based on the degree of risk the testers perceive as associated with the software being developed.Step 3: Test Software RequirementsIncomplete, inaccurate, or inconsistent requirements lead to most software failures. The inability to get requirements right during the requirements gathering phase can also increase the cost of implementation significantly. Testers, through verification, must determine that the requirements are accurate, complete, and they do not conflict with one another.

Saturday, May 31, 2008

WHITE BOX TESTING

Using white box testing method, the software engineer can drive cases that1) Guarantee that all independent paths within a module have been exercised at least once.2) Exercise all logical divisions on their true and false sides.3) Exercise all loops at their boundaries and within their operational bounds.4) Exercise internal data structures to ensure their validity.

CONTROLE STRUCTURE TESTING : This alludes to white box-testing method.1) Basic path Testing: This enables the tester to drive a logical complexity measure of a procedural design and are this measure as a guide for defining a basis set of execution paths. Test cases derived to exercise the basis set are guaranteed to execute every during testing.We may are ‘FLOW GRAPH NOTATION’ as a useful loop for understanding control flow and illustrating the approach.We can are ‘CYLLOMETRIC COMPLEXITY’ is a software metric that provides a quantitative measure of the logical complexity of a program. Here, the value computed for cyclometric complexity defines the No. of independent paths is the basis set of program and provides as with the upped bound for the No. of tests that be conducted to ensure that all statements have been exercise at least once.

window.google_render_ad();

GRAPH METRIX 2) Condition Testing :This test case design method exercise the logical condn’s contained in the program module. It has adv. like (i) measurement of test coverage of a cond’n is sample. (ii) The test coverage of condn’s is a program provides guidance for the gen of additional tests for the program.BRANCH TESTING : for a compound condn’s C, the true and false branches of C and every sample cond’n in C need to be exec. at least onceDOMAIN TESTING, required there of four tests to be derived for a relational exprsm.3) Data flow TestingThis method selects test paths of a program according to the locations of defines and cases variable in the program.4) Loop Testing:1) Start at the internal loop set all other loops to2) Conduct simple test for investment loops while holding the outer loops their min interaction parameter ( loop counter) values. Add other tests for out of range or excluded values.3) Work outward, conducting test for the next loops but keeping all other outer loops at min. values.4) Continue till the last loop.