Definition of Testing Sw testing is process to evaluate the functionality of a software application with an intent to find if the developed sw meet the requirements or not It is defined as an execution of a work product with intent to find defects ID: 1028487
Download Presentation The PPT/PDF document "Unit 2 Fundamentals of testing" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
1. Unit 2 Fundamentals of testing
2. Definition of TestingS/w testing is process, to evaluate the functionality of a software application with an intent to find if the developed s/w meet the requirements or notIt is defined as an execution of a work product with intent to find defectsTesting is done to protect the common users from any failure of system during usage.The process can include:Verifying s/w completeness in regards to functional/business requirementsIdentifying technical bugs/errors and ensuring the software is error freeAssessing usability, performance, security, localization, compatibility and installation
3. Fundamental Test ProcessTest Planning and ControlTest Analysis and DesignTest Implementation and ExecutionEvaluating Exit Criteria and ReportingTest Closure Activities
4. The Psychology of TestingComparison of the mindset of the tester and developerThe balance between self-testing and independent TestingThere should be clear and courteous communication and feedback on defects between tester and developer
5. Testing ApproachesBing bang approachIt involves testing s/w after completion of developmentIt also called ‘Final Testing’ or ‘System Testing’It is done before releasing s/wBing bang approach has main trust on black box testing of s/w to ensure that the requirements as defined and documented in requirement and design specifications are met successfully.In Bing bang approach, s/w is tested before delivery It not possible to detect all faults due to time constraints
6. Total Quality Management ApproachTQM can be defined as management technique for improving processes, products and servicesIt focuses on the entire business and NOT just on particular processDefect removal costs are approximately 10 times more after coding This is a cost associated with fixing the problems belonging to requirements, design, coding etc.
7. Testing During Development Life CycleRefer unit no. 1
8. Requirement Traceability Matrix(RTM)RTM is used to trace the requirements to the tests the are needed to verify whether the requirements are fulfilledThe purpose of the RTM is to ensure that all requirements defined for a system are tested.The RTM is usually developed in concurrency with the initial list of requirements.Types of RTM:Forward Traceability(Mapping requirements to the test cases)Backward or Reverse Traceability(Mapping test cases to requirements)
9. Advantages of RTMEntire s/w development can be tracked completely through RTMAny test case failure can be tracked through requirements, designs, coding etc.Any changes in requirements can be affected through entire work product upto test casesApplication becomes maintainableIts also helps to understand if any redundancy has been created in the applicationIt may answer questions about what is being developed
10. Problems with RTMNumber of requirements are hugeConnectivity with different relationship Requirements changes frequently and so do designs, code and test casesA customer may not find value in it and pay for itIncremental and iterative developments are the major challenges for maintaining traceability
11. Essentials of Software TestingTest StrategyStrengthsWeaknessesTesting PlanTest casesOpportunitiesTest dataThreatsTest Environment
12. WorkbenchA workbench concept is a method of scheduling that how a particular action has to be executed. Actions contain in workbench are:InputExecuteCheckProduction OutputRework
13. Important Features of Testing ProcessEasy to operateStabilityObservabilityEasy to understandDecomposability
14. Misconceptions about TestingAnyone can testTesting can happen at the endTesting can find all bugsDefects found by customers are blamed on TesterTest automation will replace manual testers.
15. Principles of Software TestingTesting shows presence of defectsExhaustive testing is not possibleEarly TestingDefect ClusteringPesticide ParadoxTesting is context dependentAbsence of errors fallacy
16. Salient features of Good TestingCapturing user requirementsBe ScepticalDon’t compromise on qualityDesign objectivesEnsure end user satisfactionThink from the users perspectiveNever Promise 100% coverageStart earlyBe open Suggestions
17. Test PolicyIt is a document described at the organization levelIt is determined by the senior management of the organizationThe test policy is very high-level document and at the top of the test documentation structureOrganizations may prefer to publish their test policy in a sentence as well as a separate documentPolicy can be used in both development and maintenance project
18. Test Policy shall describe the followingsClear answer to the questionsIt is determined by the senior management of the organisation.The definition of the testing process used by the organization to increase the quality of the software developedHow the organization will measure the effectiveness and efficiency of the test while achieving goals.How the organization will improve its test processes
19. Test StrategyIt is prepared at the program level and includes general test strategy, management principles, processes and approachesIt is also a high level document and is usually written by the test managerIt is generally prepared by the large scale projects in small scale projects, test strategies and test approach may be included in the test plan
20. Test Strategy includes:Objectives/Scope of testingIn-scope and Out-scopeTest LevelsTest types(Function/non-functional)Entry/ExitRiskTest environmentRetesting & Regression approach
21. Test PlanningAll test strategies specific to the projectTest estimations and test scheduleTest organization/roles/responsibilitiesTest deliverablesTest reporting principles
22. Testing ProcessTesting is a process rather than a single activityTest processes are a vital part of SDLCFrom planning to execution, each stage of the process is systematically plannedThis can be combined and evaluated to get expected results and outcomesThe quality and effectiveness of the s/w testing is primarily determined by the quality of the test process
23. Test Team EfficiencyIt is a very important aspect for development team and managementIf team is very efficient, less iterations of testing are requiredEvery test manager must be aware of the efficiency of his teamTest team efficiency is depend on organizational culture
24. Mutation TestingIt is used to check capability of test program and test cases to find defectsThe mutations introduced to source code are designed to imitate common programming errorsA good unit test suite typically detects the program mutations and fails automaticallyThe changes in mutant program are kept extremely small, so it does not affect the overall objective of the program
25. Challenges in TestingComplete testing is impossibleSetting the right processLack of communicationLack of recourses Test coverage
26. Test Team approachProactive communicationRole and responsibility of Team membersProgram ManagerQA LeadTest analysistTest Engineer
27. Process Problems faced by TestingUnstable EnvironmentTools being force-fedLack of feedback loopPreconceived notionsNo documentation
28. Cost aspect of TestingPrevention CostAppraisal CostInternal failure costExternal Failure Cost
29. Contents of Test Policy DocumentDefinition of TestingDescription of Test processTest evaluationQuality Level to be achievedApproach to Test process improvement
30. ErrorsErrors can be present in software due to following reasonsProgramming ErrorUnclear requirementsChanging requirementsSoftware complexityTime PressuresPoorly Documented Codes
31. DefectsDefects can be simply defined as a variance between expected and actualDefects is an error found after the application goes into productionDefects can be divided as follows:WrongMissingExtra
32. Developing Test StrategyA test strategy document is a high level document, developed by project managerIt is normally derived from the business requirement specification DocumentIt is not updated too often(Static Document)Process:Select & Rank test factors for given applicationIdentify system development phases and related test factorsIdentify associated risks with each selected test factor in case if it is not achievedIdentify phases in which risks of not meeting a test factor need to be addressed
33. Developing Testing Methodologies(Plan)Acquire and study test strategy Determine the type of development project being executedDetermine the type of software system being madeIdentify tactical risks related to developmentDetermine when testing must occur during life cycleSteps to develop customised test strategyType of development methodology impact test plan decisions
34. Testing ProcessDefining Test PolicyDefining Test strategyPreparing Test PlanEstablishing Testing Objectives for be AchievedDesigning Test Scenarios and Test casesWriting/ reviewing Test casesDefining Test DataCreation of test BedExecuting Test CasesTest resultsTest AnalysisPerforming RetestingRoot Cause analysis
35. Attitude Towards TestingIt starts from test policy and ends to test strategy definitionCross-cultural DifferencesLack of proper communicationDevelopers may not accept the defects in first placeConflict between developer and tester
36. Test methodologiesBlack box testingWhite box testingGrey box testing
37. Black box testingIn black box testing product is tested as per software specifications or requirement statement defined by business analysts/system analysts/customer.It involves testing system/components considering inputs, outputs and general functionalities as defined in requirement specificationMainly talks about the requirement specification given by customerIt does not consider any internal processing by the system This testing is with the view as if a user is testing the system.Black box functional testing is generally performed for integration testing, system testing, and acceptance testingIt is mainly driven by the test data used during testing.
38. Advantages of black box testing It is the only method to prove that software dose what it is supposed to do and is dose not do something which can cause a problem to user/customer.It is the only method to show that software is living and it really worksPerformance an security testing can be done by black box testing methodology
39. Disadvantages of black box testing Some logical errors and internal structure problems in coding can be missed in black box testingIf an application calls common function again and again, and it will be tested so many times that it leads redundant testing
40. White box testingWhite box testing is done on the basis of internal structures of software as defined by requirements, designs, coding standards and guidelines.It starts with reviews of requirements, designs and codes.Mainly deals with the structure and design of the software product.It requires that tester must have knowledge about development processes and artifacts including various platform, databases etc.Test case designing is based on how test artifacts are created and used during testing.
41. Advantages of White box testing It can check whether the coding standards, commenting reuse have been followed or notWhite box testing is the cost effective way of finding defects as it helps in reducing stage contamination.Code complexity, commenting styles and reuse can only be verified by white box testing methodologies.
42. Disadvantages of White box testing It does not ensure that user requirements are met correctlyIt does not establish whether decisions, conditions, paths and statements covered during reviews are sufficient or not for the given set of requirements.It is dominated by the use of checklists which may be retired directly in the work product and one must do a thorough analysis of all defects
43. Grey box testingGrey box testing is done on the basis of internal structures of software as defined by requirements, designs, coding standards and guidelines as well as the functional and non-functional requirement specification.It combines verification techniques with validation techniques where one can ensure that software is build correctly and also works.It talks mainly about a combination approaches, viz black and white box testing at the same.
44. Advantages of Grey box testing It checks whether the work product works in a correct manner, both functionally as well as structurally
45. Disadvantages of Grey box testing Knowledge of some automation tools along with their configuration is essential for performing grey box testing.
46. Raising Management Awareness for TestingManagement should be made aware of the importance of testing a product because the funds required will be provided by them.Without adequate funding for testing, software quality suffers.Benefits of s/w testing are enormous QualitySatisfied CustomerBringing ProfitUser ExperienceBusiness Optimisation
47. Skills Required by TesterUnderstanding Business needsGood communication skillsConcepts of TestingLevels of TestingKnowing what to prioritizeContinuous LearningTechniques for validation and verificationRisk assessment and managementDeveloping Test planExecution of test plan
48. REFERENCE :Software Quality Assurance by Tech-Max PublicationSoftware Quality Assurance by SHETH PublicationSoftware Testing: Principles, Techniques and Tools by M. G. Limaye