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 system under load. modeling the expected usage of a software program by simulating multiple users accessing the program's services concurrently.
Load Testing
software testing
Defect density
Agile Testing

2. GUI testing is the process of testing a graphical user interface to ensure it meets its written specifications
GUI Testing
Branch coverage
Dynamic Testing
white box testing

3. Testing software through executing it.
Bottom-up Testing
Grey Box Testing
Dynamic Testing
quality assurance process improvement

4. An analysis method that determines which parts of the software have been executed (covered) by the test case suite and which parts have not been executed and therefore may require additional attention.
Bugs
Incremental testing
Code coverage
Endurance Testing

5. 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
Bottom-up Testing
test coverage
architecure of SOA
Agile Testing

6. 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
Keyword driven Testing
Conformance Testing / Compliance Testing / Standards Testing
Boundary value analysis/ testing
Beta Testing / Field Testing

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.
Logic coverage Testing / Logic driven Testing / Structural
Defect
Basis Path Testing
Grey Box Testing

8. This technique for testing computer software does not require significant advanced planning and is tolerant of limited documentation for the target-of-test.
test coverage
Isolation Testing
Exploratory Testing
CAST

9. The process of testing to determine the interoperability of a software product
Interoperability testing
Grey Box Testing
white box testing
Efficiency testing

10. 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
Back-to-back testing
Dynamic Testing
Endurance Testing
Equivalence Class

11. 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
Fault
Decision table testing
Ad-hoc Testing
Installation Testing

12. Tests that use representative sets of programs and data designed to evaluate the performance of computer hardware and software in a given configuration
Benchmark Testing
Invalid testing
Beta Testing / Field Testing
providing information - metric

13. Testing whether the system meets its specified objectives for maintainability.
Maintenance testing
Maintainability Testing / Serviceability Testing
Context Driven Testing
enough of testing

14. Checks for memory leaks or other problems that may occur with prolonged execution
Endurance Testing
black box testing
best practice
Equivalence partition Testing

15. 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
test coverage
Decision condition testing
Efficiency testing
Integration Testing

16. 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.
Acceptance Testing/User Acceptance Testing
Decision coverage
Boundary value analysis/ testing
Decision testing

17. Provide critical information during project
providing information Objective
Exploratory Testing
Exhaustive Testing
SOA

18. Testing in which test cases are designed based on variable usage within the code.
architecure of SOA
Coverage Testing
AUT
Data flow Testing

19. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.
Back-to-back testing
Gamma testing
stop testing timing
Equivalence partition Testing

20. Testing using input values that should be rejected by the component or system
Benchmark Testing
Model Based Testing
Invalid testing
Defect density

21. The typical grey box tester is permitted to set up or manipulate the testing environment - like seeding a database
Acceptance Testing/User Acceptance Testing
Grey Box Testing
Decision condition testing
Component Testing

22. A white box test design technique in which test cases are designed to execute condition outcomes and decision outcomes
Exhaustive Testing
Accessibility Testing
Decision condition testing
Equivalence Class

23. Knows about the software and test - no proper plan
Installation Testing
backend testing/database testing
Component Testing
exploratory testing

24. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent
SOA
white box testing
Branch testing
Basis Path Testing

25. Approach to doing something that generally give good results when applied appropriately and thoughfully
Statement coverage
structural testing
best practice
Gamma testing

26. A white box test design technique in which test cases are designed to execute decision outcomes
CAST
SOA
Decision testing
High order tests

27. Computer Aided Software Testing
Endurance Testing
CAST
Monkey Testing
backend testing/database testing

28. Depends on the schedule and risk based - business impact follow the 20-80 rules
Installation Testing
Bugs
Branch coverage
stop testing timing

29. 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
Accessibility Testing
structural testing
Decision testing
Quality

30. This term refers to making software specifically designed for a specific locality
Localization Testing
GUI Testing
Heuristic evaluations
Maintenance testing

31. Testing whether the system is compatible with other systems with which it should communicate.
Compatibility Testing
Logic coverage Testing / Logic driven Testing / Structural
best practice
Development testing

32. 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
Compatibility Testing
Acceptance Testing/User Acceptance Testing
Maintainability Testing / Serviceability Testing
Integration Testing

33. 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
Decision coverage
Decision table testing
Arc Testing / Branch Testing
Integration Testing

34. 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.
Authorization Testing
Exhaustive Testing
Monkey Testing
Interoperability testing

35. Integration testing where system components are integrated into the system one at a time until the entire system is integrated.
AUT
functional testing
Incremental testing
Equivalence Class

36. Testing concerned with the accuracy of documentation.
Load Testing
Documentation Testing
Isolation Testing
Decision table testing

37. The expected results or performance characteristics that define whether the test cases passed or failed
Bottom-up Testing
Design based Testing
Acceptance criteria
providing information Objective

38. A variation of Regression Testing. Testing conducted with multiple cycles in which errors found in test cycle N are resolved and the solution is retested in test cycle N+.
N+ Testing
Authorization Testing
structural testing
Statement coverage

39. An organizational structure consists of activities such as task allocation & coordination and supervision which are directed towards the achievement of organizational aims.[citation needed]
organisation structure
Dynamic Testing
Branch
test coverage

40. Testing conducted to evaluate whether systems or components pass data and control correctly to each other.
Interface Testing
organisation structure
High order tests
Beta Testing / Field Testing

41. A test that exercises a feature of a product in full detail.
Depth Testing
Acceptance criteria
Interoperability testing
Dependency Testing

42. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes
Boundary value analysis/ testing
Bottom-up Testing
Business process-based testing
Black Box Testing / Functional Testing

43. 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.
Decision testing
Fuzz Testing
Back-to-back testing
Testing best practice

44. Kind of unit testing - internal working of software
structural testing
Gamma testing
Bottom-up Testing
Back-to-back testing

45. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes
Equivalence Partitioning
test coverage
Coverage Testing
Breadth Testing

46. Test case design
Dependency Testing
Logic coverage Testing / Logic driven Testing / Structural
Defect density
best practice

47. Testing practice for projects using agile methodologies - treating development as the customer of testing and emphasizing a test-first design paradigm
Agile Testing
providing information Objective
Statement coverage
white box testing

48. 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.
Loop Testing
Accessibility Testing
Decision condition testing
Model Based Testing

49. Testing of programs or procedures used to convert data from existing systems for use in replacement systems.
End-to-end Testing
Ad-hoc Testing
enough of testing
Conversion Testing / Migration Testing

50. A white box testing technique that exercises program loops
Exploratory Testing
Dependency Testing
black box testing
Loop Testing