Test your basic knowledge |

Software Testing And Qa

Subject : it-skills
Instructions:
  • Answer 50 questions in 15 minutes.
  • If you are not ready to take this test, you can study here.
  • Match each statement with the correct term.
  • Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.

This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.
1. They arise from mistakes and errors made by people in either a program's source code or its design that prevents it from working correctly or produces an incorrect result






2. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.






3. Black-box tests conducted once the software has been integrated






4. A test that a user/sponsor and manufacturer/producer jointly perform on a finished - engineered product/system through black-box testing - as functional test & beta test & QA test & application test & confidence test & final test or end user test






5. The percentage of decision outcomes that have been exercised by a test suite.






6. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent






7. Testing whether the system meets its specified objectives for maintainability.






8. Form of independent - interoperable services that can be composed and recomposed to fulfill multiple business requirements. . Each service internally accesses resources including databases - business rules - client devices






9. Involves testing the systems responsible for the initiation and maintenance of user sessions. This will require testing the Input validation of login fields & Cookie security and Lockout testing . permitting unauthorised access.






10. The expected results or performance characteristics that define whether the test cases passed or failed






11. Test activity aimed at proving the correct implementation of a required function at a level where the entire hardware/software chain involved in the execution of the function is available.






12. Once the alpha phase is complete development enters the beta phase. Versions of the software known as beta-versions are released to a limited audience outside of the company to ensure that the product has few faults or bugs. black box






13. Integration testing where system components are integrated into the system one at a time until the entire system is integrated.






14. Coverage testing is concerned with the degree to which test cases exercise or cover the logic (source code) of the software module or unit. It is also a measure of coverage of code lines & code branches and code branch combinations






15. A white box testing technique that exercises program loops






16. A white box test case design techniques that uses the algorithmic flow of the program to design tests






17. Testing a system or an Application on the fly - i.e just few tests here and there to ensure the system or an application does not crash out






18. A basic block that can be selected for execution based on a program construct in which one of two or more alternative program path is available






19. Can't see - test the functional testing - no access to code and testing is done on UI






20. Back end Testing means DataBase Testing. Normally a software product/application uses GUI front end for easyuser interaction.






21. This technique for testing computer software does not require significant advanced planning and is tolerant of limited documentation for the target-of-test.






22. Testing which covers all combinations of input values and preconditions for an element of the software under test






23. An approach to integration testing where the lowest level components are tested first - then used to facilitate the testing of higher level components. The process is repeated until the component at the top of the hierarchy is tested.






24. A test case design technique for a component in which test cases are designed to execute branch outcomes. A test method satisfying coverage criteria that require that for each decision point - each possible branch be executed at least once.






25. An anomaly or flaw in a delivered work product. found during early lifecycle phases A defect can be any kind of issue you want tracked and resolved.






26. A white box test design technique in which test cases are designed to execute decision outcomes






27. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes






28. The process of testing to determine the interoperability of a software product






29. Root cause analyst - base of the problem - customer satisfaction report






30. Testing conducted to evaluate whether systems or components pass data and control correctly to each other.






31. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes






32. Testing software through executing it.






33. A black box test design techniques in which test cases are designed to execute the combinations of inputs and/or stimuli (causes) shown in a decision table






34. Determine whether a system meets some specified standard. external organization as complying with the standard






35. Multi-user testing geared towards determining the effects of accessing the same application code - module or database records. Identifies and measures the level of locking - deadlocking and use of single-threaded code and locking semaphores






36. Fuzz testing is a software testing technique. The basic idea is to attach the inputs of a program to a source of random data. extremely simple and free of preconceptions about system behavior.






37. Black box testing - concrete box or functional testing is used to check that the outputs of a program - given certain inputs - conform to the functional specification of the program. It performs testing based on previously understood requirements (or






38. An accidental condition that causes the failure of a component in the implementation model to perform its required behavior. A fault is the root cause of one or more defects identified by observing one or more failures.






39. Integration testing is the phase of software testing in which individual software modules are combined and tested as a group. It follows unit testing and precedes system testing






40. Testing one particular module - functionality heavily






41. Testing in which test cases are designed based on variable usage within the code.






42. A variation of Regression Testing. Testing conducted with multiple cycles in which errors found in test cycle N are resolved and the solution is retested in test cycle N+.






43. Checks for memory leaks or other problems that may occur with prolonged execution






44. Depends on the schedule and risk based - business impact follow the 20-80 rules






45. Testing concerned with the accuracy of documentation.






46. The process of testing to determine the efficiency of a software product






47. Approach to doing something that generally give good results when applied appropriately and thoughfully






48. Testing of programs or procedures used to convert data from existing systems for use in replacement systems.






49. This term refers to making software specifically designed for a specific locality






50. Testing using input values that should be rejected by the component or system