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. A white box test design technique in which test cases are designed to execute decision outcomes






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






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






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






5. Testing one particular module - functionality heavily






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






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






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






9. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.






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






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






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






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






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






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






16. Computer Aided Software Testing






17. Provide critical information during project






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






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






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






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






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






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






24. Test case design






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






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






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. The percentage of decision outcomes that have been exercised by a test suite.






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






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






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






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






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






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






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






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






37. executing the software






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






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






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






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






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






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






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






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






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






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






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






49. Testing concerned with the accuracy of documentation.






50. Kind of unit testing - internal working of software