1.

Testing Life Cycle Test Analysis -> Test Plan -> Test Case design -> Test execution -> Test log (Defect tracking) -> Test Report 2.Reliability Vs Correctness Less faults is correctness Less failure is reliability A system may be reliable but not correct 3.Different V&V methods Walkthroughs Inspections Reviews 4. Definitions of all types of testing i) Black Box Testing This is also called as Functional Testing, Knowing the specified function that the program has been designed to perform and conducting tests to demonstrate the function is fully operational. In this testing the Functionality of the program is only considered and the input and the output is properly accepted and the integrity of external information is maintained It does not concentrate on how the program works internally to achieve the functionality. ii) White Box Testing This is also called Glass Box Testing Or Structural Testing Or Dynamic testing.. Knowing the internal logic of the program, Tests are conducted to ensure that the internal operations of the program perform as mentioned in the SRS.In this testing all the internal paths are not checked but it is important to find a limited number of logical paths be selected and executed iii) Unit Testing This is a glass box testing methodology, which concentrates on internal logic of the program under testing, Verification of the program code in the coding phase is called as unit testing, This testing is generally done by the developer to ensure that the internal working of the program is as specified in SRS. The reference document for unit testing is the Module design document from which the program is been translated into the programming language. iv) Integration Testing Integration is testing is done by combining independent modules which to form a sub system, Here stubs and drivers are used to simulate the actual behavior of the sub system. Here Testing is concentrated on the issues how the modules are coupled, and the communication between the modules and interface between the modules in thoroughly

Testing the new build to ensure that the previous functionality is not effected by executing the tests cases which are success full on the previous version are build. This testing is performed to ensure the system is fully functional as specified in SRS. viii) Ad-hoc Testing Testers who are very comfortable on the application on which they are testing do this testing. this only a validation exercise.N/W.N/W.S/W. xi) Configuration Testing This testing is performed to check out how the performance of the system works in differenments such as H/W. v) System Testing System testing is done by integration all the module to form the complete system as stated in the SRS document. Here a test suite is used. First testing should be done to ensure that the previous functionality of the program is not disturbed by fixing errors or adding new functionality. ix) Sanity Testing This is the initial testing performed when the new build is available in order to check out whether the build is ready for further Or major testing. xii) Compatibility Testing How well the system performs in a particular H/W.S/W. this testing is done randomly without any test cases with the intend of finding errors. x) Recovery Testing This testing is done to check out how system can be brought back to its normal function when it's integrity of the system fails. and tests conducted on the entire system is called as system testing.H/W. Performing tests to verify how good the system works in different configurations of S/W. xiii) Security Testing This testing is done with intend to check out how far the system can withstand to external threat.tested. and to ensure the integrity of the system is properly maintained.N/W. This testing is performed to check out whether to check out the application can be accepted for further testing. . The reference document for system testing is SRS Document. vi) Regression Testing When new versions or builds come for testing. The reference document for this testing is design document. a test suite is one which contains interesting test cases and their expected results for future use. vii) Functionality Testing Nothing but Black box testing. Independent modules may work fine but they may show some abnormal Functionality when coupled with other models in order check such things integration testing is performed.

xx) User Acceptance Testing This is a system level testing generally done at the client’s environment. This testing is done with the realistic data of the client to find out errors. xxi) Smoke Testing Is also called sanity testing. xxii) Exploratory testing often taken to mean a creative. Testing the application how well it performs at peak loads and at abnormal conditions. testers may be learning the software as they test it . informal software test that is not based on formal test plans or test cases. complex data base queries.xiv) Alpha Testing This testing is done at the system testing level. this testing is done to check out at what point of load the system performance of the system degrades. xvii) Stress Testing This testing is done by subjecting the system to abnormal conditions such as heavy load. The reference document for this testing is client requirements. large integer values and performing the same operation a number times to find out at what point the system breaks. xix) User Interface Testing This testing is done to check out the user interface or for cosmetic errors. xvi) Load Testing This testing is performed to check how the system can withstand for heavy loads. This testing is intended the look and feel of the application as specified in the design document. xv) Beta Testing This Testing is done before the final release of the s/w to end-users. Before the final release of the s/w is released to users for testing where there will be no controlled conditions and the user here is free enough to do what ever he wants to do on the system to find errors. before the s/w is been released to the end user. the system is tested by people who do not have good knowledge of the system this testing is done at the developer place under controlled conditions and under the supervision of the developers. xviii) Performance Testing This can be interchanged with the load and stress testing. This type of testing is called beta testing.

9. 6. It includes the management and the man required for testing. It describes what all types of testing are to include and depth of testing. in order to verify that the system behaves correctly for the correct test cases and wrongly for the incorrect test cases. 8. Testing procedure in your organization In our org the project leaders takes care of all the activities of testing. In an Equilance partition for 1 set of correct test cases 2 sets of incorrect test cases are taken.a method for determining if a set of test data or test cases is useful. What is Stub & Driver? . It identifies the risks involved in testing. This meeting is with the intent of raising the problems and this is not a problem solving session. Boundary Value Analysis & Equivalence Partition The system works well for certain sets of data as specified in test cases. What is Test Data? Test data is the minimal data required to execute a program under testing. objective and the procedure that are to be followed for testing. It includes the automated testing tools that are to use while testing. 10. Test plan is also designed and documented by the proj leader. What is the Test Plan and explain the contents of that Test plan is a document that consists of the scope. by deliberately introducing various code changes ('bugs') and retesting with the original test data/cases to determine if the 'bugs' are detected. 7. After the test cases are executed the test reports are been reported to the proj lead who takes care of the further activities to be done. that is the data nearer to the upper bound and lower bound of the set these conditions are to be tested. It contains the parts of the program. The tests are verified by the proj lead. but the system may behave abnormally at the boundaries of the set. and which need no testing. What is a Review? Have you involved in Review? Review is a formal presentation of s/w design to customer.xxiii) Mutation testing . It defines the test environment that is needed for testing and the resources. here the solutions of the problem is left to the producer of the review then and there or after the meeting with the help of one or more individuals. which are to be tested. Proper implementation requires large computational resources 5. Equilance partition is a set of test cases where the successful execution of any test case in the clause guarantees the success of all the test cases. It defines the number of test cases to be developed for each functionality. management and technical staff in the form of meeting.

User behavior are Unpredictable and uncontrollable System variables are firewalls. Making sure that any agreed upon standards is followed and ensure that problems are found and dealt with. What is the difference between Client Server Testing & Web Testing? Client Server Testing Transactions are limited User behavior are predictable and controllable System variables are LAN. It is oriented to prevention. 15. certification audit is like an examination .result is the certification is pass or fail. Applicable for all types of orginations. What is your Bug Clearance Ratio? (Ratio between the valid and invalid bugs) 96:100 12. S/W Failures are notice internally Web Testing Transactions are unlimited. What are CMM.the result if assessment is quantative score of maturity of s/w development process ISO is generic Model. Process is defined the execution. 11. which is designed to perform a intended functionality 16. Centralized H/W. Procedure is tested with the intend to increase its quality. ISO processes and what is the difference between them? CMM is maturity Model is applicable for s/w.contains 18 Key processing areas. 14. Stub is program which acts as a calling program for the module to be tested to simulate the functionality of the module under testing. 13. What is Quality Assurance & Quality Control? Quality assures it involves in the entire life cycle and it controls and monitors the improving the process. hoisting company caching systems Failures are notice externally. routers. which accepts the input data and produces the output data. Procedure is one. For this purpose the stubs and drivers are used which have the minimal functionality of the actual modules Driver is programming which acts as a main program for the module to be tested.contains 20 clauses.During integration testing the modules are combined to form subsystem but in this process some modules may not be ready for integration. What is the difference between Management System & Quality Management System? . final assessment is collabrative. Quality control is systematic approach of controlling the changes and implementing the changes that are needed at different levels of s/w development. What is Process & Procedure? Process is tested with the intend to improve it.

Quality management system is involved only at the level of testing to achieve the full functionality of the s/w system as described in the srs document. 21) When do you stop testing? It is difficult to determine when to stop testing as changes occur frequently in development life cycle in each every phase. Testing budget is over. 19) What is Audit? The ease with the system is checked with the standards.Management system is involved in the entire life cycle of the s/w. What is Quality Monitoring & Quality Measurement? Quality Monitoring is checking the conformance of system to the explicitly defined functional and performance requirements. 22) How do you rate yourself in Testing? 7-8 23) How do you rate yourself in achieving deadline? If required i will put my complete efforts for the achieving deadlines 24. What is Walkthrough? A formal meeting or a review for evaluation or informational purpose. explicitly documented standards and implicitly defined characteristics expected are achieved. When all the test cases are passed with certain level.QC Vs QA QC Walkthrough Testing Inspection Check point review 25.Role of Testing: QA Quality Audit Defining process Selection of Tools Training . Alpha and beta testing period expires. the subject of inspection is the srs and the test plan and the purpose is to find the problems and see what is missing but not fix any thing. 17. which includes from the analysis phase to the implementation phase. When the bug rate falls to a certain low level. 18. 20) What is Inspection? Inspection is more formalized than a walk through.

Is a demonstration of error / apparent correctness. user predefined procedures. and experimentation freedom. rigid. 26. Theory of testing available Much of test design and execution can be auto mated. dull. Should be planned. scheduled. Must be done by the insider. Impossible without design knowledge. end cannot be predicted. Cannot be constrained Is a deductive process Vindicates a programmer Demands intuitive leaps. Only recently have theorists started looking into it. constrained.Primary: • Determine whether system meets specifications • Determines whether system meets needs. conjectures. Debugging Unknown initial conditions. . and inhuman. predictable outcomes. Secondary: • Instill confidence • Provide insight into the software development process • Continuously improve the testing process. Much can be done without design knowledge. designed. Proves programmers “ failure” Should strive to be predictable. Automation still a dream.N o 1 2 3 4 5 6 7 8 9 27 Testing Starts with known conditions. Can be done by outsider. S.

Sign up to vote on this title
UsefulNot useful