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 carried out using no recognised test case design technique. It is also known as Exploratory Testing






2. Testing concerned with the accuracy of documentation.






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






4. Test case design






5. Computer Aided Software Testing






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






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






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






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






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






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






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






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






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






15. Application Under Test






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






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






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






19. This term refers to making software specifically designed for a specific locality






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






21. Testing one particular module - functionality heavily






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






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






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






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






26. executing the software






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






28. Provide critical information during project






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






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






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






32. The testing of individual software components.






33. Stakeholder stakeholder satisfaction with test results report






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






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






36. Approach to doing something that generally give good results when applied appropriately and thoughfully






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






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






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






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






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






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






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






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






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






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






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






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






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






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







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