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






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






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






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






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






6. Designing tests based on objectives derived from the architectural or detail design of the software (e.g. - tests that execute specific invocation paths or probe the worst case behaviour of algorithms).






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






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






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






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






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






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






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






14. The testing of individual software components.






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






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






17. Test case design






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






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






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






21. The expected results or performance characteristics that define whether the test cases passed or failed






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






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






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






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






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






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






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






29. A portion of a component's input or output domains for which the component's behaviour is assumed to be the same from the component's specification






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






31. Provide critical information during project






32. A white box testing technique that exercises program loops






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






34. Defined as any testing that occurs outside of the development environment. installed on. simply appear to be to run a setup program - can be used with confidence






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






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






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






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






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






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






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






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






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






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






45. Testing one particular module - functionality heavily






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






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






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






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






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