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. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned






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






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






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






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






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






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






8. Testing the changes to an operational system or the impact of a changed environment to an operational system






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






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






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






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






13. Provide critical information during project






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






15. Testing software through executing it.






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






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






18. The process of testing to determine the efficiency of a software product






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






20. Testing concerned with the accuracy of documentation.






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






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






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






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






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






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






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






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






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






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






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






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






34. executing the software






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






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






37. Depends on the schedule and risk based - business impact follow the 20-80 rules






38. Stakeholder stakeholder satisfaction with test results report






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






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






41. Test case design






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






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






44. Fuzz testing is a software testing technique. The basic idea is to attach the inputs of a program to a source of random data. extremely simple and free of preconceptions about system behavior.






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






46. Kind of unit testing - internal working of software






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






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






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






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