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 conducted to evaluate whether systems or components pass data and control correctly to each other.






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






3. executing the software






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






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






6. Root cause analyst - base of the problem - customer satisfaction report






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






8. Depends on the schedule and risk based - business impact follow the 20-80 rules






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






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






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






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






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






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






15. This technique for testing computer software does not require significant advanced planning and is tolerant of limited documentation for the target-of-test.






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






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






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






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






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






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






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






23. Testing concerned with the accuracy of documentation.






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






25. A service oriented architecture (SOA) is a design model which relies on a collection of loosely coupled self contained services that communicate with each other through the internet and can be called from multiple clients in a standard fashion






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






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






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






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






30. Computer Aided Software Testing






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






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






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






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






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






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






37. Testing one particular module - functionality heavily






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






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






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






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






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






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






45. Stakeholder stakeholder satisfaction with test results report






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






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






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






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






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







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