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. Testing in which two or more variants of a component or system are executed with the same inputs - the outputs compared and analyzed in cases of discrepancies






2. A portion of a component's input or output domains for which the component's behaviour is assumed to be the same from the component's specification






3. Similar to black box testing - structure of test cases in order to find defects and its strutured






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






5. executing the software






6. GUI testing is the process of testing a graphical user interface to ensure it meets its written specifications






7. Examines an application's requirements for pre-existing software - initial states and configuration in order to maintain proper functionality






8. 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.






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






10. The typical grey box tester is permitted to set up or manipulate the testing environment - like seeding a database






11. Designing tests based on objectives derived from the architectural or detail design of the software (e.g. - tests that execute specific invocation paths or probe the worst case behaviour of algorithms).






12. Gamma testing is a little-known informal phrase that refers derisively to the release of "buggy" (defect-ridden) products.






13. Flavor of Agile Testing that advocates continuous and creative evaluation of testing opportunities in light of the potential information revealed and the value of that information to the organization right now.






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






15. Tests that use representative sets of programs and data designed to evaluate the performance of computer hardware and software in a given configuration






16. 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+.






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






18. Kind of unit testing - internal working of software






19. A system under load. modeling the expected usage of a software program by simulating multiple users accessing the program's services concurrently.






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






21. Computer Aided Software Testing






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






23. A test that exercises a feature of a product in full detail.






24. Integration testing where no incremental testing takes place prior to all the system's components being combined to form the system.






25. Testing concerned with the accuracy of documentation.






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






27. An analysis method that determines which parts of the software have been executed (covered) by the test case suite and which parts have not been executed and therefore may require additional attention.






28. Provide critical information during project






29. The number of defects identified in a component or system divided by the size of the component or system (expressed in standard measurement terms - e.g. lines-ofcode or number of classes or function points)






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






31. Risk based questions - depends on the schedule and risk based - business impact follow the 20-80 rules






32. Testing carried out using no recognised test case design technique. It is also known as Exploratory Testing






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






34. 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






35. The testing of individual software components.






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






37. 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






38. A test suite that exercises the full functionality of a product but does not test features in detail






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






40. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned






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






42. Measure of amount of testing performed . determined by mapping test cases to requirements - Tracebility matrix is test coverage. Number of test caes executed divided by total number of test cases






43. Testing the changes to an operational system or the impact of a changed environment to an operational system






44. Testing one particular module - functionality heavily






45. 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






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






47. 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.






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






49. Test case design






50. Application Under Test







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests