software testing

678 views

Published on

Published in: Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
678
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

software testing

  1. 1. IMPLEMENTATION OF McCABE’S METRICS AIM: . To measure the given software implementation using McCabe’s metrics and test it by path testing method. TEST PLANNING: 1. Test strategy  Scope of testing To test the path of implementation using McCabe’s metrics.  Test deliverables To test the measurements of the given program using C language. • the cyclomatic complexity using the formula V(G)=e-n+2  Tools used win runner & C programming. 2. Test plan It is a document to say what to test, when to test, how to test, who to test. • What to test- cyclomatic complexity using McCabe’s metrics. • How to test-by using Win Runner. • who to test- Developer. 3. Test bed- Win Runner and C programming language. TEST DEVELOPMENT: Test cases i. Edges ii. Nodes iii. Regions
  2. 2. TEST EXECUTION: Step1: Draw a flow chart for given software implementation (to find greatest of 3 numbers). Step2: Draw a flow graph for the program from the flow chart. Step3: Count the no of edges (e) and no of nodes (n) and regions(r). Step4: Find the cyclomatic complexity using the formula V(G)=e-n+2 MCCABE’S METRICS FLOWCHART: START INPUT a,b,c If a >b If b>a &b>c &b>c b is grater c is grater a is grater STOP
  3. 3. CALCULATION OF MC’CABE’S METRICS: 0 1 2 4 3 5 6 7 V(G)=e-n+2 e=9 n=7 V(G)=9-7+2 =4
  4. 4. TEST RESULT ANALYSIS: Step1: Initialize the win runner Start programs win runner win runner Step2: Create a new html document to be tested and save it on the desktop Step3: In win runner create a new task Step4: Click on record button and open the saved html file Step5: Then click on stop button the file will be recorded automatically Step6: Then click on the button Run from top, This will automatically give the test result as Pass: If executed with out errors Fail: If executed with some errors And the execution time will also be displayed Step7: Then go to Tools GUI Map Editor And save the file at some location say for example “desktop”.
  5. 5. RESULT: Once the test meets the exit criteria the activities such as capturing the key output lessons learned result,logs,documents related to the project are achieved and used as reference for next project .

×