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. executing the software






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






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






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






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






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






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






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






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






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






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






12. Verifying a product is accessible to the people having disabilities (deaf or blind or mentally disabled etc.).






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






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






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






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






17. Testing software through executing it.






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






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






20. The testing of individual software components.






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






22. A white box testing technique that exercises program loops






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






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






25. Testing one particular module - functionality heavily






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






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






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






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






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






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






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






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






34. Provide critical information during project






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






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






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






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






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






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






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






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






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






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






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






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






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






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






49. The percentage of branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage






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