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. Application Under Test






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






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






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






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






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






7. Stakeholder stakeholder satisfaction with test results report






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






9. Computer Aided Software Testing






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






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






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






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






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






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






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






17. Testing concerned with the accuracy of documentation.






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






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






20. The testing of individual software components.






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. GUI testing is the process of testing a graphical user interface to ensure it meets its written specifications






23. Provide critical information during project






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






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






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






27. Kind of unit testing - internal working of software






28. Test case design






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






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






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. Testing the changes to an operational system or the impact of a changed environment to an operational system






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






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






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






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






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






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






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






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. Back end Testing means DataBase Testing. Normally a software product/application uses GUI front end for easyuser interaction.






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






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






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






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






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






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






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






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