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 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.
Boundary value analysis/ testing
AUT
Mutation testing
Defect

2. 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
Gorilla Testing
Beta Testing / Field Testing
Grey Box Testing
quality assurance process improvement

3. The testing of individual software components.
Defect
Mutation testing
Component Testing
Conformance Testing / Compliance Testing / Standards Testing

4. Component testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs
Decision table testing
GUI Testing
Isolation Testing
Model Based Testing

5. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.
Back-to-back testing
Alpha Testing
Basis Path Testing
Model Based Testing

6. Provide critical information during project
Design based Testing
Statement coverage
Defect
providing information Objective

7. It is a whole - is the whole process form review to plans strategy and whole thing
Boundary value analysis/ testing
QA
enough of testing
best practice

8. 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
Coverage Testing
Acceptance Testing/User Acceptance Testing
Data flow Testing
Back-to-back testing

9. 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.
Testing best practice
Maintenance testing
End-to-end Testing
Mutation testing

10. 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
Gamma testing
Mutation testing
Black Box Testing / Functional Testing
Depth Testing

11. 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.
Arc Testing / Branch Testing
Branch testing
Maintenance testing
SOA

12. A white box test design technique in which test cases are designed to execute condition outcomes and decision outcomes
Fuzz Testing
stop testing timing
Decision condition testing
Acceptance Testing/User Acceptance Testing

13. Tests that use representative sets of programs and data designed to evaluate the performance of computer hardware and software in a given configuration
High order tests
Benchmark Testing
Development testing
Depth Testing

14. 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.
best practice
Maintenance testing
Fault
organisation structure

15. Testing in which test cases are designed based on variable usage within the code.
stop testing timing
Data flow Testing
Invalid testing
Data-Driven Testing

16. 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.
Big Bang Testing
Model Based Testing
Logic coverage Testing / Logic driven Testing / Structural
Defect

17. Approach to doing something that generally give good results when applied appropriately and thoughfully
Equivalence partition Testing
best practice
Branch coverage
Monkey Testing

18. Checks for memory leaks or other problems that may occur with prolonged execution
Grey Box Testing
Maintenance testing
Context Driven Testing
Endurance Testing

19. Verifying a product is accessible to the people having disabilities (deaf or blind or mentally disabled etc.).
Design based Testing
Accessibility Testing
Interface Testing
Integration Testing

20. 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
quality assurance process improvement
Heuristic evaluations
Efficiency testing
Load Testing

21. Root cause analyst - base of the problem - customer satisfaction report
Bugs
Back-to-back testing
Data flow Testing
quality assurance process improvement

22. Testing concerned with the accuracy of documentation.
Monkey Testing
Fuzz Testing
Defect density
Documentation Testing

23. Testing one particular module - functionality heavily
Authorization Testing
High order tests
Dynamic Testing
Gorilla Testing

24. 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
best practice
Quality
Basis Path Testing
Fault

25. 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
Equivalence partition Testing
Integration Testing
architecure of SOA
Branch coverage

26. GUI testing is the process of testing a graphical user interface to ensure it meets its written specifications
Basis Path Testing
Invalid testing
GUI Testing
AUT

27. Back end Testing means DataBase Testing. Normally a software product/application uses GUI front end for easyuser interaction.
Fuzz Testing
Design based Testing
Logic coverage Testing / Logic driven Testing / Structural
backend testing/database testing

28. Depends on the schedule and risk based - business impact follow the 20-80 rules
Development testing
stop testing timing
Fault
Accessibility Testing

29. Black-box tests conducted once the software has been integrated
Exhaustive Testing
Conformance Testing / Compliance Testing / Standards Testing
Fuzz Testing
High order tests

30. Testing the changes to an operational system or the impact of a changed environment to an operational system
AUT
Maintenance testing
Documentation Testing
Gorilla Testing

31. Kind of unit testing - internal working of software
Ad-hoc Testing
Mutation testing
Arc Testing / Branch Testing
structural testing

32. Application Under Test
Defect
SOA
Bottom-up Testing
AUT

33. 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.
GUI Testing
Fuzz Testing
Interoperability testing
quality assurance process improvement

34. A test that exercises a feature of a product in full detail.
Depth Testing
Code coverage
Invalid testing
Development testing

35. Testing conducted to evaluate whether systems or components pass data and control correctly to each other.
Interface Testing
Monkey Testing
Endurance Testing
Isolation Testing

36. 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.
Keyword driven Testing
QA
Installation Testing
High order tests

37. Testing using input values that should be rejected by the component or system
exploratory testing
Dependency Testing
Invalid testing
Defect density

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]
organisation structure
Integration Testing
Authorization Testing
Fuzz Testing

39. 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
Design based Testing
Installation Testing
Exploratory Testing
Branch testing

40. A system under load. modeling the expected usage of a software program by simulating multiple users accessing the program's services concurrently.
Load Testing
Logic coverage Testing / Logic driven Testing / Structural
Equivalence Class
Fault

41. Knows about the software and test - no proper plan
Boundary value analysis/ testing
exploratory testing
Bottom-up Testing
test coverage

42. A white box testing technique that exercises program loops
Endurance Testing
Loop Testing
GUI Testing
Fault

43. Computer Aided Software Testing
Equivalence partition Testing
white box testing
CAST
Defect density

44. Testing practice for projects using agile methodologies - treating development as the customer of testing and emphasizing a test-first design paradigm
Agile Testing
Equivalence Class
Branch testing
High order tests

45. This technique for testing computer software does not require significant advanced planning and is tolerant of limited documentation for the target-of-test.
Integration Testing
Fault
Decision coverage
Exploratory Testing

46. The process of testing to determine the efficiency of a software product
High order tests
Arc Testing / Branch Testing
Efficiency testing
Endurance Testing

47. 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.
Context Driven Testing
Branch testing
Localization Testing
Ad-hoc Testing

48. Test case design
Basis Path Testing
architecure of SOA
Logic coverage Testing / Logic driven Testing / Structural
providing information - metric

49. 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
Branch testing
End-to-end Testing
Equivalence Class
Interoperability testing

50. A white box test design technique in which test cases are designed to execute decision outcomes
Localization Testing
best practice
Decision testing
Dependency Testing