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. The process of testing to determine the interoperability of a software product






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






3. Testing practice for projects using agile methodologies - treating development as the customer of testing and emphasizing a test-first design paradigm






4. A scripting technique that uses data files to contain not only test data and expected results but also keywords related to the application being tested.






5. A testing methodology in which two or more program mutations are executed using the same test cases to evaluate the ability of the test cases to detect differences in the mutations






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






7. Application Under Test






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






9. Testing software through executing it.






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






11. executing the software






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






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






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






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






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






17. Informal method of usability inspection in the field of human-computer interaction. identifying the usability problems . involves evaluators examining the interface and judging its compliance






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






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






20. The percentage of executable statements that have been exercised by a test suite.






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






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






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






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






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. The percentage of branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage






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






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






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






30. It is a whole - is the whole process form review to plans strategy and whole thing






31. 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).






32. The totality of features and characteristics of a product or service that bears its ability to satisfy stated or implied needs." defined by ISO 8402 1986






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






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






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






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






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






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






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






40. Kind of unit testing - internal working of software






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






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






43. A test case design technique for a component in which test cases are designed which include representatives of boundary values - the defined limits of an output domain.






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






45. Testing one particular module - functionality heavily






46. Knows about the software and test - no proper plan






47. Component testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs






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






49. A white box test design technique in which test cases are designed to execute branches.






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







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