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






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






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






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






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






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






7. Provide critical information during project






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






9. Measure of amount of testing performed . determined by mapping test cases to requirements - Tracebility matrix is test coverage. Number of test caes executed divided by total number of test cases






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






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. A white box test design technique in which test cases are designed to execute decision outcomes






13. Integration testing where system components are integrated into the system one at a time until the entire system is integrated.






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






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






16. GUI testing is the process of testing a graphical user interface to ensure it meets its written specifications






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






18. executing the software






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






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






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






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






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






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. Test case design






26. The testing of individual software components.






27. Stakeholder stakeholder satisfaction with test results report






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






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






30. Testing one particular module - functionality heavily






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






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






33. Testing software through executing it.






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






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






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






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






38. The process of testing to determine the interoperability of a software product






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






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






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






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






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






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






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






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






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






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






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






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







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