Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Learn software testing with tech partnerz 3


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Learn software testing with tech partnerz 3

  1. 1. Learn Software TestingWith TechPartnerzSession 3
  2. 2. Your Partner for Professional Success © 2013 TechPartnerzSoftware Configuration management is an umbrella activity that is appliedthroughout the software process. SCM identifies controls, audits and reportsmodifications that invariably occur while software is being developed and after ithas been released to a customer. All information produced as part of softwareengineering becomes of software configuration. The configuration is organized ina manner that enables orderly control of change.The following is a sample list of Software Configuration Items: Management plans (Project Plan, Test Plan, etc.) Specifications (Requirements, Design, Test Case, etc.) Customer Documentation (Implementation Manuals, User Manuals,Operations Manuals, On-line help Files) Source Code (PL/1 Fortran, COBOL, Visual Basic, Visual C, etc.) Executable Code (Machine readable object code, exes, etc.) Libraries (Runtime Libraries, Procedures, %include Files, APIs, DLLs, etc.) Databases (Data being Processed, Data a program requires, test data,Regression test data, etc.) Production DocumentationConfiguration Management
  3. 3. Your Partner for Professional Success © 2013 TechPartnerzTest DevelopmentTest ExecutionTestAnalysisTest DesignButterfly Model of Test Development
  4. 4. Your Partner for Professional Success © 2013 TechPartnerzAnalysis is the key factor which drives in any planning. During theanalysis, the analyst understands the following:• Verify that each requirement is tagged in a manner that allowscorrelation of the tests for that requirement to the requirement itself.(Establish Test Traceability)• Verify traceability of the software requirements to systemrequirements.• Inspect for contradictory requirements.• Inspect for ambiguous requirements.• Inspect for missing requirements.• Check to make sure that each requirement, as well as thespecification as a whole, is understandable.• Identify one or more measurement, demonstration, or analysismethod that may be used to verify the requirement’s implementation(during formal testing).• Create a test “sketch” that includes the tentative approach andindicates the test’s objectives.Test Analysis
  5. 5. Your Partner for Professional Success © 2013 TechPartnerzDuring Test Analysis the required documents will be carefully studied bythe Test Personnel, and the final Analysis Report is documented.The following documents would be usually referred:1. Software Requirements Specification.2. Functional Specification.3. Architecture Document.4. Use Case Documents.The Analysis Report would consist of the understanding of theapplication, the functional flow of the application, number of modulesinvolved and the effective Test Time.Test Analysis
  6. 6. Your Partner for Professional Success © 2013 TechPartnerzThe right wing of the butterfly represents the act of designing and implementingthe test cases needed to verify the design artifact as replicated in theimplementation. Like test analysis, it is a relatively large piece of work.Unlike test analysis, however, the focus of test design is not to assimilateinformation created by others, but rather to implement procedures,techniques, and data sets that achieve the test’s objective(s).The outputs of the test analysis phase are the foundation for test design. Eachrequirement or design construct has had at least one technique (ameasurement, demonstration, or analysis) identified during test analysis thatwill validate or verify that requirement. The tester must now implement theintended technique.Software test design, as a discipline, is an exercise in the prevention, detection,and elimination of bugs in software. Preventing bugs is the primary goal ofsoftware testing. Diligent and competent test design prevents bugs fromever reaching the implementation stage. Test design, with its attendant testanalysis foundation, is therefore the premiere weapon in the arsenal ofdevelopers and testers for limiting the cost associated with finding and fixingbugs.Test Design
  7. 7. Your Partner for Professional Success © 2013 TechPartnerzDuring Test Design, basing on the Analysis Report the testPersonnel would develop the following:Test Plan.Test Approach.Test Case documents.Performance Test Parameters.Performance Test Plan.Test Design
  8. 8. Your Partner for Professional Success © 2013 TechPartnerzAny test case should adhere to the following principals:Accurate – tests what the description says it will test.Economical – has only the steps needed for its purpose.Repeatable – tests should be consistent, no matter who/when it isexecuted.Appropriate – should be apt for the situation.Traceable – the functionality of the test case should be easily found.Test Execution
  9. 9. Your Partner for Professional Success © 2013 TechPartnerzDuring the Test Execution phase, keeping the Project and the Testschedule, the test cases designed would be executed. The followingdocuments will be handled during the test execution phase:1. Test Execution Reports.2. Daily/Weekly/monthly Defect Reports.3. Person wise defect reports.After the Test Execution phase, the following documents would besigned off.1. Project Closure Document.2. Reliability Analysis Report.3. Stability Analysis Report.4. Performance Analysis Report.5. Project Metrics.Test Execution
  10. 10. Your Partner for Professional Success © 2013 TechPartnerzDefect Tracking Process.The Tester/Developer findsthe Bug.Reports the Defect in theDefect Tracking Tool. Status“Open”The concerned Developer isinformedThe Developer fixes the DefectThe Developer changes theStatus to “Resolved”The Tester Re-Tests andchanges Status to “Closed”If the Defect re-occurs, thestatus changes to “Re-Open”
  11. 11. Your Partner for Professional Success © 2013 TechPartnerzThis section defines a defect Severity Scale framework for determiningdefect criticality and the associated defect Priority Levels to be assignedto errors found software.The defects can be classified as follows:Critical: There is s functionality block. The application is not able toproceed any further.Major: The application is not working as desired. There are variations inthe functionality.Minor: There is no failure reported due to the defect, but certainlyneeds to be rectified.Cosmetic: Defects in the User Interface or Navigation.Suggestion: Feature which can be added for betterment.Defect Classification
  12. 12. Your Partner for Professional Success © 2013 TechPartnerzThe priority level describes the time for resolution of the defect. Thepriority level would be classified as follows:Immediate: Resolve the defect with immediate effect.At the Earliest: Resolve the defect at the earliest, on priority at thesecond level.Normal: Resolve the defect.Later: Could be resolved at the later stages.Defect Priority.
  13. 13. Your Partner for Professional Success © 2013 TechPartnerzThe Deliverables from the Test team would include the following:Test Plan.Test Case Documents.Defect Reports.Status Reports (Daily/weekly/Monthly).Test Scripts (if any).Metric Reports.Product Sign off Document.Deliverables.
  14. 14. Your Partner for Professional Success © 2013 TechPartnerzEnd of session
  15. 15. Your Partner for Professional Success © 2013 TechPartnerzThank YouFor any queries feel free to contact TechPartnerzinfo@techpartnerz.comFollow TechPartnerz on facebook, Linkedin, twitter