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. 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
Localization Testing
Testing best practice
software testing
Integration Testing

2. A white box test design technique in which test cases are designed to execute branches.
enough of testing
Grey Box Testing
Maintenance testing
Branch testing

3. 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.
Bottom-up Testing
test coverage
CAST
Accessibility Testing

4. executing the software
enough of testing
Logic coverage Testing / Logic driven Testing / Structural
software testing
Interoperability testing

5. 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
providing information Objective
Context Driven Testing
white box testing

6. 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.
Fuzz Testing
white box testing
Decision condition testing
Maintainability Testing / Serviceability Testing

7. 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
Depth Testing
Bottom-up Testing
CAST

8. Determine whether a system meets some specified standard. external organization as complying with the standard
Conformance Testing / Compliance Testing / Standards Testing
Compatibility Testing
Defect density
test coverage

9. 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
Bugs
Business process-based testing
providing information - metric
Data flow Testing

10. 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
Conformance Testing / Compliance Testing / Standards Testing
Heuristic evaluations
quality assurance process improvement
Quality

11. A white box testing technique that exercises program loops
Loop Testing
Maintenance testing
Endurance Testing
Data-Driven Testing

12. Kind of unit testing - internal working of software
stop testing timing
End-to-end Testing
white box testing
structural testing

13. 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
N+ Testing
Maintenance testing
Maintainability Testing / Serviceability Testing

14. 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.
Accessibility Testing
Maintenance testing
Boundary value analysis/ testing
Loop Testing

15. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent
Invalid testing
Conformance Testing / Compliance Testing / Standards Testing
white box testing
Alpha Testing

16. 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
Branch
N+ Testing
Coverage Testing
CAST

17. 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
Installation Testing
Endurance Testing
Efficiency testing
Agile Testing

18. 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
Dependency Testing
Agile Testing
Gamma testing
architecure of SOA

19. This term refers to making software specifically designed for a specific locality
Conversion Testing / Migration Testing
Defect
structural testing
Localization Testing

20. The expected results or performance characteristics that define whether the test cases passed or failed
Decision testing
organisation structure
Quality
Acceptance criteria

21. This technique for testing computer software does not require significant advanced planning and is tolerant of limited documentation for the target-of-test.
Exploratory Testing
Statement coverage
Concurrency Testing
Component Testing

22. Can't see - test the functional testing - no access to code and testing is done on UI
Bottom-up Testing
black box testing
Integration Testing
Decision testing

23. 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
Equivalence Class
Beta Testing / Field Testing
AUT
Localization Testing

24. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned
Integration Testing
Testing best practice
High order tests
Component Testing

25. Knows about the software and test - no proper plan
Compatibility Testing
exploratory testing
Exhaustive Testing
Logic coverage Testing / Logic driven Testing / Structural

26. 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
Acceptance Testing/User Acceptance Testing
Model Based Testing
Defect density
Big Bang Testing

27. 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
Bugs
Conversion Testing / Migration Testing
SOA
Black Box Testing / Functional Testing

28. 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
Black Box Testing / Functional Testing
Keyword driven Testing
exploratory testing
architecure of SOA

29. 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.
Efficiency testing
Keyword driven Testing
Equivalence Class
Breadth Testing

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

31. Testing conducted to evaluate whether systems or components pass data and control correctly to each other.
black box testing
Interface Testing
Big Bang Testing
Context Driven Testing

32. Testing carried out using no recognised test case design technique. It is also known as Exploratory Testing
Ad-hoc Testing
Exhaustive Testing
Monkey Testing
Efficiency testing

33. The testing of individual software components.
Quality
Component Testing
Black Box Testing / Functional Testing
Coverage Testing

34. Formal or informal testing conducted during the implementation of a component or system usually in the development environment by developers
Development testing
Defect
Basis Path Testing
Branch coverage

35. Testing whether the system is compatible with other systems with which it should communicate.
Exhaustive Testing
Compatibility Testing
functional testing
Back-to-back testing

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]
Alpha Testing
Accessibility Testing
Defect density
organisation structure

37. Back end Testing means DataBase Testing. Normally a software product/application uses GUI front end for easyuser interaction.
Data flow Testing
backend testing/database testing
Branch coverage
Conversion Testing / Migration Testing

38. Examines an application's requirements for pre-existing software - initial states and configuration in order to maintain proper functionality
Conformance Testing / Compliance Testing / Standards Testing
Bottom-up Testing
Dependency Testing
AUT

39. The number of defects identified in a component or system divided by the size of the component or system (expressed in standard measurement terms - e.g. lines-ofcode or number of classes or function points)
Interoperability testing
Defect
Defect density
Beta Testing / Field Testing

40. The process of testing to determine the efficiency of a software product
Logic coverage Testing / Logic driven Testing / Structural
SOA
Efficiency testing
Benchmark Testing

41. Testing software through executing it.
Back-to-back testing
Dynamic Testing
Design based Testing
Bugs

42. Testing whether the system meets its specified objectives for maintainability.
Development testing
Maintainability Testing / Serviceability Testing
Back-to-back testing
Fault

43. Depends on the schedule and risk based - business impact follow the 20-80 rules
Testing best practice
stop testing timing
Basis Path Testing
Decision testing

44. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.
Load Testing
Equivalence partition Testing
Authorization Testing
Acceptance criteria

45. Black-box tests conducted once the software has been integrated
High order tests
providing information - metric
Equivalence partition Testing
End-to-end Testing

46. 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
Decision testing
Monkey Testing
Branch testing
Beta Testing / Field Testing

47. 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
exploratory testing
Decision table testing
Business process-based testing
test coverage

48. Testing one particular module - functionality heavily
Coverage Testing
Fuzz Testing
Gorilla Testing
Branch coverage

49. The process of testing to determine the interoperability of a software product
Testing best practice
Data flow Testing
Interoperability testing
High order tests

50. Component testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs
Documentation Testing
Efficiency testing
Isolation Testing
Coverage Testing