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. An organizational structure consists of activities such as task allocation & coordination and supervision which are directed towards the achievement of organizational aims.[citation needed]






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






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






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






5. Testing one particular module - functionality heavily






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






24. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned






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






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






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






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






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






30. Testing concerned with the accuracy of documentation.






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






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






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






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






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






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






37. A white box testing technique that exercises program loops






38. Provide critical information during project






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






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






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






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






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






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






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






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






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






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






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






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







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