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. A white box testing technique that exercises program loops






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






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






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






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






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






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






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






10. Kind of unit testing - internal working of software






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






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






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






14. Testing one particular module - functionality heavily






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 scripting technique that uses data files to contain not only test data and expected results but also keywords related to the application being tested.






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






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






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






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






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






22. Testing concerned with the accuracy of documentation.






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






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






25. Provide critical information during project






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






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






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






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






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






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






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






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






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






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






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






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






38. Stakeholder stakeholder satisfaction with test results report






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






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






41. Computer Aided Software Testing






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






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






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






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






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






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






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






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






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







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