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. Knows about the software and test - no proper plan






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






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






4. Test case design






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






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






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






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






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






10. Computer Aided Software Testing






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






12. It is a whole - is the whole process form review to plans strategy and whole thing






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






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






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






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






17. Flavor of Agile Testing that advocates continuous and creative evaluation of testing opportunities in light of the potential information revealed and the value of that information to the organization right now.






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






19. Checks for memory leaks or other problems that may occur with prolonged execution






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






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






22. Testing software through executing it.






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






24. A test suite that exercises the full functionality of a product but does not test features in detail






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






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






27. Provide critical information during project






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






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






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






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






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






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






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






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






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






37. executing the software






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






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






40. A white box testing technique that exercises program loops






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






42. The testing of individual software components.






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






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






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






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






47. Testing concerned with the accuracy of documentation.






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






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






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