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






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






4. Test case design






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






6. Testing software through executing it.






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






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






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






10. Model-based testing refers to software testing where test cases are derived in whole or in part from a model that describes some (usually functional) aspects of the system under test.






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






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






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






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






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






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






17. Formal or informal testing conducted during the implementation of a component or system usually in the development environment by developers






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






19. Testing whether the system is compatible with other systems with which it should communicate.






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






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






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






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






24. Defined as any testing that occurs outside of the development environment. installed on. simply appear to be to run a setup program - can be used with confidence






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






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






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






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






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






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






31. Kind of unit testing - internal working of software






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






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






34. Testing in which the action of a test case is parameterized by externally defined data values - maintained as a file or spreadsheet. A common technique in Automated Testing






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






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






37. Stakeholder stakeholder satisfaction with test results report






38. Provide critical information during project






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






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






41. A white box testing technique that exercises program loops






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






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






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






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






46. An organizational structure consists of activities such as task allocation & coordination and supervision which are directed towards the achievement of organizational aims.[citation needed]






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






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






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






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







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