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 test that exercises a feature of a product in full detail.






4. Computer Aided Software Testing






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






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






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. A white box test case design techniques that uses the algorithmic flow of the program to design tests






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






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






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






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






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






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






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






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. Root cause analyst - base of the problem - customer satisfaction report






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






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






20. executing the software






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






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






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






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






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






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






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






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






29. Black box testing - concrete box or functional testing is used to check that the outputs of a program - given certain inputs - conform to the functional specification of the program. It performs testing based on previously understood requirements (or






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






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






32. Test case design






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






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






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






36. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes






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






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






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






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






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






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






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






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






45. Provide critical information during project






46. Testing software through executing it.






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






48. Testing concerned with the accuracy of documentation.






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






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







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