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 whether the system meets its specified objectives for maintainability.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






17. Testing software through executing it.






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






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






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






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






22. Provide critical information during project






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






24. Computer Aided Software Testing






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






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






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






28. Testing a system or an Application on the fly - i.e just few tests here and there to ensure the system or an application does not crash out






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






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






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






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






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






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






35. Testing concerned with the accuracy of documentation.






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






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






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






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






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






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






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






43. A white box testing technique that exercises program loops






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






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






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






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






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






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






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







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