Software_testing

qas: question: What is the purpose of testing software?
answers: text: finding software bugs
is_impossible: no

question: Why is it so difficult to locate bugs in software?
answers: text: tests for even simple software components is practically infinite
is_impossible: no

question: What can come from one bug being fixed?
answers: text: it can illuminate other, deeper bugs,
is_impossible: no

question: What is the number of tests for complex software components?
is_impossible: yes

question: Firmware testing uses strategy to accomplish what?
is_impossible: yes

question: software testing attempts to eliminate a program for what reason?
is_impossible: yes

question: The job of testing is called what type of progress?
is_impossible: yes

question: What are some complications of not fixing bugs?
is_impossible: yes

question: What do developers commonly do when creating software that can lead to failures?
is_impossible: yes

question: What does specialization-based testing aim to test?
is_impossible: yes

question: What two methods can be used when using Load Testing?
is_impossible: yes
context: As the number of possible tests for even simple software components is practically infinite, all software testing uses some strategy to select tests that are feasible for the available time and resources. As a result, software testing typically (but not exclusively) attempts to execute a program or application with the intent of finding software bugs (errors or other defects). The job of testing is an iterative process as when one bug is fixed, it can illuminate other, deeper bugs, or can even create new ones.

qas: question: What can testing not completely find?
answers: text: all the defects
is_impossible: no

question: While looking for bugs, what else can testing do?
answers: text: furnishes a criticism or comparison
is_impossible: no

question: What does the software compare during testing against?
answers: text: oracles—principles or mechanisms
is_impossible: no

question: What make up the oracle during testing?
answers: text: specifications, contracts, comparable products, past versions
is_impossible: no

question: Testing can identify all the defects within what?
is_impossible: yes

question: While looking for bug, what can testing not do?
is_impossible: yes

question: What are some things oracles include and are limited to?
is_impossible: yes

question: What does the software contrast during testing against?
is_impossible: yes

question: What is the secondary problem  with running software testing?
is_impossible: yes

question: What are some complications of not fixing bugs?
is_impossible: yes

question: Development Testing attempts to eliminate instruction errors before code is promoted where?
is_impossible: yes
context: Although testing can determine the correctness of software under the assumption of some specific hypotheses (see hierarchy of testing difficulty below), testing cannot identify all the defects within software. Instead, it furnishes a criticism or comparison that compares the state and behavior of the product against oracles—principles or mechanisms by which someone might recognize a problem. These oracles may include (but are not limited to) specifications, contracts, comparable products, past versions of the same product, inferences about intended or expected purpose, user or customer expectations, relevant standards, applicable laws, or other criteria.

qas: question: What is the primamry reason for testing software?
answers: text: to detect software failures
is_impossible: no

question: What can testing software not fully completely establish?
answers: text: cannot establish that a product functions properly under all conditions
is_impossible: no

question: What does the scope of testing the software also look at?
answers: text: examination of code as well as execution of that code
is_impossible: no

question: Which two teams would you normally separate when writing and testing software?
answers: text: testing organization may be separate from the development team
is_impossible: no

question: What is a secondary purpose of testing software?
is_impossible: yes

question: What does software testing always include?
is_impossible: yes

question: In the previous culture of software development, what two things were separate?
is_impossible: yes

question: Data from software testing may be used to model what?
is_impossible: yes

question: The tester chooses outputs to accomplish what?
is_impossible: yes

question: What is involved with White-box testing?
is_impossible: yes

question: Why are alpha version made available to the public?
is_impossible: yes
context: A primary purpose of testing is to detect software failures so that defects may be discovered and corrected. Testing cannot establish that a product functions properly under all conditions but can only establish that it does not function properly under specific conditions. The scope of software testing often includes examination of code as well as execution of that code in various environments and conditions as well as examining the aspects of code: does it do what it is supposed to do and do what it needs to do. In the current culture of software development, a testing organization may be separate from the development team. There are various roles for testing team members. Information derived from software testing may be used to correct the process by which software is developed.

qas: question: What is the first step that leads to a software failure?
answers: text: programmer makes an error
is_impossible: no

question: What is the result of the programmer making a mistake?
answers: text: defect (fault, bug)
is_impossible: no

question: When can software defects in dead code cause problems?
answers: text: run on a new computer hardware platform
is_impossible: no

question: Software programs evolve through what process?
is_impossible: yes

question: All defects result in what?
is_impossible: yes

question: Defects in dead code always do what?
is_impossible: yes

question: When the environment is changed, what does a failure always result from?
is_impossible: yes

question: What can a single defect not result in?
is_impossible: yes

question: An external perspective is used in white-box testing as well as what else is used to develop test cases?
is_impossible: yes

question: Which two procedures are used to design test cases in White-box testing?
is_impossible: yes

question: What are these test (level testing) typically grouped by?
is_impossible: yes
context: Software faults occur through the following processes. A programmer makes an error (mistake), which results in a defect (fault, bug) in the software source code. If this defect is executed, in certain situations the system will produce wrong results, causing a failure. Not all defects will necessarily result in failures. For example, defects in dead code will never result in failures. A defect can turn into a failure when the environment is changed. Examples of these changes in environment include the software being run on a new computer hardware platform, alterations in source data, or interacting with different software. A single defect may result in a wide range of failure symptoms.

qas: question: What is the primary issue with running software testing?
answers: text: testing under all combinations of inputs and preconditions (initial state) is not feasible
is_impossible: no

question: What types of software bugs are difficult to find during testing?
answers: text: defects that occur infrequently
is_impossible: no

question: What other non-functional dimensions can cause software to underperform and cause other problems?
answers: text: usability, scalability, performance, compatibility, reliability
is_impossible: no

question: What is the secondary problem  with running software testing?
is_impossible: yes

question: Defects that occur frequently are how easy to find?
is_impossible: yes

question: What are examples of functional dimensions of quality?
is_impossible: yes

question: What is the issue with the functional dimensions of quality?
is_impossible: yes

question: What is the purpose of testing software?
is_impossible: yes

question: There are three classes, what has been concluded and proven for all classes?
is_impossible: yes

question: What type of software would have a better defect tolerance?
is_impossible: yes
context: A fundamental problem with software testing is that testing under all combinations of inputs and preconditions (initial state) is not feasible, even with a simple product.:17-18 This means that the number of defects in a software product can be very large and defects that occur infrequently are difficult to find in testing. More significantly, non-functional dimensions of quality (how it is supposed to be versus what it is supposed to do)—usability, scalability, performance, compatibility, reliability—can be highly subjective; something that constitutes sufficient value to one person may be intolerable to another.

qas: question: Although software developers are unable to test everything, what do they run to keep the testing to a minimum? 
answers: text: use combinatorial test design
is_impossible: no

question: What does the use of combinatorial testing consist of?
answers: text: get greater test coverage with fewer tests
is_impossible: no

question: What two types of testing are involved with combinatorial testing as mentioned here?
answers: text: speed or test depth
is_impossible: no

question: What test do firmware developers use to find out how to keep testing to a minimum?
is_impossible: yes

question: Combinatorial test design does not allow users to get what?
is_impossible: yes

question: Unstructured variations can be built into what items?
is_impossible: yes

question: "Coverage" is referring to combined coverage but not what?
is_impossible: yes

question: What is the result of the programmer making a mistake?
is_impossible: yes

question: When can dynamic testing occur?
is_impossible: yes

question: What is Operational Acceptance limited to while testing?
is_impossible: yes
context: Software developers can't test everything, but they can use combinatorial test design to identify the minimum number of tests needed to get the coverage they want. Combinatorial test design enables users to get greater test coverage with fewer tests. Whether they are looking for speed or test depth, they can use combinatorial test design methods to build structured variation into their test cases. Note that "coverage", as used here, is referring to combinatorial coverage, not requirements coverage.

qas: question: What determines the cost of fixing a bug?
answers: text: the earlier a defect is found
is_impossible: no

question: Ho many more times would the cost be if the problem is found after the software's release?
answers: text: 10–100 times more
is_impossible: no

question: What could possibly lessen the cost of fixing buggy software?
answers: text: cloud-based services
is_impossible: no

question: What is the unpopular belief about the cost of fixing a bug?
is_impossible: yes

question: The cost of fixing a defect does not depend on what?
is_impossible: yes

question: How much less would it cost to fix a problem found after the software's release?
is_impossible: yes

question: What modern items may increase the cost of re-deployment over time?
is_impossible: yes

question: It has been disproved that each class is included into what?
is_impossible: yes

question: When is the distinction between black and grey box not important?
is_impossible: yes

question: While looking for bugs, what else can testing do?
is_impossible: yes
context: It is commonly believed that the earlier a defect is found, the cheaper it is to fix it. The following table shows the cost of fixing the defect depending on the stage it was found. For example, if a problem in the requirements is found only post-release, then it would cost 10–100 times more to fix than if it had already been found by the requirements review. With the advent of modern continuous deployment practices and cloud-based services, the cost of re-deployment and maintenance may lessen over time.

qas: question: Name three approaches software testers take when testing their software?
answers: text: Reviews, walkthroughs, or inspections
is_impossible: no

question: What is the term that is used to described executing programmed code with a given set of test?
answers: text: dynamic testing
is_impossible: no

question: When can dynamic testing occur?
answers: text: before the program is 100% complete
is_impossible: no

question: What are commonly used techniques during dynamic testing?
answers: text: stubs/drivers or execution from a debugger environment
is_impossible: no

question: There are few approached in what type of testing?
is_impossible: yes

question: Examples of static testing include previews, walkthroughs, and what other item?
is_impossible: yes

question: Dynamic testing refers to executing predetermined code with what?
is_impossible: yes

question: When does dynamic testing not take place?
is_impossible: yes

question: Static testing is always what?
is_impossible: yes

question: Volume Testing is a way to test firmware when?
is_impossible: yes

question: Defects that occur frequently are how easy to find?
is_impossible: yes

question: When is the distinction between black and grey box not important?
is_impossible: yes
context: There are many approaches available in software testing. Reviews, walkthroughs, or inspections are referred to as static testing, whereas actually executing programmed code with a given set of test cases is referred to as dynamic testing. Static testing is often implicit, as proofreading, plus when programming tools/text editors check source code structure or compilers (pre-compilers) check syntax and data flow as static program analysis. Dynamic testing takes place when the program itself is run. Dynamic testing may begin before the program is 100% complete in order to test particular sections of code and are applied to discrete functions or modules. Typical techniques for this are either using stubs/drivers or execution from a debugger environment.

qas: question: What is another term used for White-box testing?
answers: text: clear box testing
is_impossible: no

question: What is involved with White-box testing?
answers: text: by seeing the source code
is_impossible: no

question: Which two procedures are used to design test cases in White-box testing?
answers: text: testing an internal perspective of the system, as well as programming skills
is_impossible: no

question: White-box data testing is also known by what other names?
is_impossible: yes

question: An external perspective is used in white-box testing as well as what else is used to develop test cases?
is_impossible: yes

question: The tester chooses outputs to accomplish what?
is_impossible: yes

question: What is in-circulus testing also known as?
is_impossible: yes

question: What is the result of the programmer making a mistake?
is_impossible: yes

question: It has been disproved that each class is included into what?
is_impossible: yes

question: What can black-box testing sometimes be referred to with the in-ability to see the code?
is_impossible: yes
context: White-box testing (also known as clear box testing, glass box testing, transparent box testing and structural testing, by seeing the source code) tests internal structures or workings of a program, as opposed to the functionality exposed to the end-user. In white-box testing an internal perspective of the system, as well as programming skills, are used to design test cases. The tester chooses inputs to exercise paths through the code and determine the appropriate outputs. This is analogous to testing nodes in a circuit, e.g. in-circuit testing (ICT).

qas: question: What is the main difference between black-box testing and white-box testing?
answers: text: seeing the source code
is_impossible: no

question: What are the software testers aware of?
answers: text: aware of what the software is supposed to do
is_impossible: no

question: What are the first three methods mentioned that make up black-box testing??
answers: text: equivalence partitioning, boundary value analysis
is_impossible: no

question: Black-box testing treats data as what?
is_impossible: yes

question: Testers are always aware of what?
is_impossible: yes

question: What are the first three methods of white-box testing?
is_impossible: yes

question: Black-box testing works with seeing what type of code?
is_impossible: yes

question: What does the tester execute while performing certain actions?
is_impossible: yes

question: What two methods can be used when using Load Testing?
is_impossible: yes

question: What are some complications of not fixing bugs?
is_impossible: yes
context: Black-box testing treats the software as a "black box", examining functionality without any knowledge of internal implementation, without seeing the source code. The testers are only aware of what the software is supposed to do, not how it does it. Black-box testing methods include: equivalence partitioning, boundary value analysis, all-pairs testing, state transition tables, decision table testing, fuzz testing, model-based testing, use case testing, exploratory testing and specification-based testing.

qas: question: What term is used to test functionality of the software accordingly with the application requirements?
answers: text: Specification-based testing
is_impossible: no

question: What are the test cases built around?
answers: text: specifications and requirements
is_impossible: no

question: When building test cases which of the two methods used is more common over the other?
answers: text: functional
is_impossible: no

question: What does specialization-based testing aim to test?
is_impossible: yes

question: Test cases are built around specializations and what else?
is_impossible: yes

question: Out of the two methods of building test cases, non-functional and unfunctional, which is more common?
is_impossible: yes

question: What descriptions of the firmware are used in test cases?
is_impossible: yes

question: What certification requires applicants to demonstrate ability?
is_impossible: yes

question: What method is used that involved syncopation of an application?
is_impossible: yes

question: Knowing the overlying concepts of how software works helps testers how?
is_impossible: yes
context: Specification-based testing aims to test the functionality of software according to the applicable requirements. This level of testing usually requires thorough test cases to be provided to the tester, who then can simply verify that for a given input, the output value (or behavior), either "is" or "is not" the same as the expected value specified in the test case. Test cases are built around specifications and requirements, i.e., what the application is supposed to do. It uses external descriptions of the software, including specifications, requirements, and designs to derive test cases. These tests can be functional or non-functional, though usually functional.

qas: question: What is one huge advantage to using the black-box method?
answers: text: no programming knowledge is required
is_impossible: no

question: What can black-box testing sometimes be referred to with the in-ability to see the code?
answers: text: like a walk in a dark labyrinth without a flashlight.
is_impossible: no

question: What is a good reason to have testers and developers separate?
answers: text: tester likely has a different set and may emphasize different areas of functionality
is_impossible: no

question: What knowledge is required for the black box technique?
is_impossible: yes

question: Black-box coding has been compared to what?
is_impossible: yes

question: Some parts of the program can remain untested because the what law is not examined?
is_impossible: yes

question: Testers and developers are kept together for what reason?
is_impossible: yes

question: What are commonly used techniques during dynamic testing?
is_impossible: yes

question: What is the result of the programmer making a mistake?
is_impossible: yes

question: What method is used that involved syncopation of an application?
is_impossible: yes
context: One advantage of the black box technique is that no programming knowledge is required. Whatever biases the programmers may have had, the tester likely has a different set and may emphasize different areas of functionality. On the other hand, black-box testing has been said to be "like a walk in a dark labyrinth without a flashlight." Because they do not examine the source code, there are situations when a tester writes many test cases to check something that could have been tested by only one test case, or leaves some parts of the program untested.

qas: question: What does grey-box testing involve?
answers: text: having knowledge of internal data structures and algorithms
is_impossible: no

question: What does a grey-box tester not need to run their test?
answers: text: not required to have full access to the software's source code
is_impossible: no

question: What does not qualify as grey-box testing?
answers: text: Manipulating input data and formatting output
is_impossible: no

question: Grey-box testing involves having knowledge of external data structures and what else?
is_impossible: yes

question: The tester is required to have full access to what piece of information?
is_impossible: yes

question: Manipulating data and formatting input do not qualify as what?
is_impossible: yes

question: When is the distinction between black and grey box not important?
is_impossible: yes

question: Who performs the Unit testing phase?
is_impossible: yes

question: Firmware testing uses strategy to accomplish what?
is_impossible: yes

question: Development Testing attempts to eliminate instruction errors before code is promoted where?
is_impossible: yes
context: Grey-box testing (American spelling: gray-box testing) involves having knowledge of internal data structures and algorithms for purposes of designing tests, while executing those tests at the user, or black-box level. The tester is not required to have full access to the software's source code.[not in citation given] Manipulating input data and formatting output do not qualify as grey-box, because the input and output are clearly outside of the "black box" that we are calling the system under test. This distinction is particularly important when conducting integration testing between two modules of code written by two different developers, where only the interfaces are exposed for test.

qas: question: What dopes a typical grey-box tester sets up?
answers: text: an isolated testing environment
is_impossible: no

question: What does the tester execute while performing certain actions?
answers: text: SQL statements
is_impossible: no

question: What does a grey-box tester implement when they have limited information?
answers: text: intelligent test scenarios
is_impossible: no

question: Knowing the overlying concepts of how software works helps testers how?
is_impossible: yes

question: A black-box tester will usually be able to set up what type of testing environment?
is_impossible: yes

question: What does the tester execute while preforming certain queries?
is_impossible: yes

question: Based on lengthy information, what does grey-box testing implement?
is_impossible: yes

question: The tester is required to have full access to what piece of information?
is_impossible: yes

question: With several certifications out there that can be aquired, what is the one trait they all share?
is_impossible: yes

question: Volume Testing is a way to test firmware when?
is_impossible: yes
context: By knowing the underlying concepts of how the software works, the tester makes better-informed testing choices while testing the software from outside. Typically, a grey-box tester will be permitted to set up an isolated testing environment with activities such as seeding a database. The tester can observe the state of the product being tested after performing certain actions such as executing SQL statements against the database and then executing queries to ensure that the expected changes have been reflected. Grey-box testing implements intelligent test scenarios, based on limited information. This will particularly apply to data type handling, exception handling, and so on.

qas: question: What are the four recognized levels of testing software?
answers: text: unit testing, integration testing, component interface testing, and system testing
is_impossible: no

question: What are these test (level testing) typically grouped by?
answers: text: software development process, or by the level of specificity of the test
is_impossible: no

question: What is defined in the SWEBOK guide as to testing the main levels?
answers: text: unit-, integration-, and system testing
is_impossible: no

question: What are the other levels classified by?
answers: text: the testing objective
is_impossible: no

question: What are the four unrecognized levels of tests?
is_impossible: yes

question: How are test infrequently grouped?
is_impossible: yes

question: What defines all the levels of the development process?
is_impossible: yes

question: The levels covered in the SWEBOK guide are unit-, reintegration, and what other level?
is_impossible: yes

question: What is classified by the pretesting objective?
is_impossible: yes

question: Which two procedures are used to design test cases in White-box testing?
is_impossible: yes

question: What is one example of failure testing?
is_impossible: yes

question: What test do firmware developers use to find out how to keep testing to a minimum?
is_impossible: yes
context: There are generally four recognized levels of tests: unit testing, integration testing, component interface testing, and system testing. Tests are frequently grouped by where they are added in the software development process, or by the level of specificity of the test. The main levels during the development process as defined by the SWEBOK guide are unit-, integration-, and system testing that are distinguished by the test target without implying a specific process model. Other test levels are classified by the testing objective.

qas: question: What is the main reasoning behind Unit testing that involves synchronization of the application on a broad spectrum? 
answers: text: reduce software development risks, time, and costs
is_impossible: no

question: Who performs the Unit testing phase?
answers: text: software developer or engineer
is_impossible: no

question: What does Unit testing look to eliminate?
answers: text: construction errors
is_impossible: no

question: By elimination construction errors, what is the expected end result?
answers: text: increase the quality of the resulting software
is_impossible: no

question: Unit testing is a firmware development that involves what?
is_impossible: yes

question: Unit testing is preformed by the architect or what kind of developer?
is_impossible: yes

question: Instead of reducing traditional QA focuses, unit testing does what to it?
is_impossible: yes

question: Unit testing tries to eliminate collaboration errors before what?
is_impossible: yes

question: While looking for bugs, what else can testing do?
is_impossible: yes

question: Development Testing attempts to eliminate instruction errors before code is promoted where?
is_impossible: yes

question: This approach only works when half of the modules of the same what are ready?
is_impossible: yes
context: Unit testing is a software development process that involves synchronized application of a broad spectrum of defect prevention and detection strategies in order to reduce software development risks, time, and costs. It is performed by the software developer or engineer during the construction phase of the software development lifecycle. Rather than replace traditional QA focuses, it augments it. Unit testing aims to eliminate construction errors before code is promoted to QA; this strategy is intended to increase the quality of the resulting software as well as the efficiency of the overall development and QA process.

qas: question: What is it called to check data passed between units?
answers: text: component interface testing
is_impossible: no

question: What is it called when data is being passed?
answers: text: message packets
is_impossible: no

question: What is an option  of component interface testing  used while sending message packets?
answers: text: keep a separate log file of data items being passed
is_impossible: no

question: What is a variation of black-box testing?
answers: text: Component interface testing
is_impossible: no

question: What can be used to check the databases passed between units?
is_impossible: yes

question: What is another name for the data being possessed? 
is_impossible: yes

question: What is one option for interface integration?
is_impossible: yes

question: Usual data values in an interface can be used to explain what?
is_impossible: yes

question: What is a variation of black-boxing testing?
is_impossible: yes

question: What method is used that involved syncopation of an application?
is_impossible: yes

question: What is the most common cause for software failure?
is_impossible: yes

question: What type of testing comes before alpha testing?
is_impossible: yes
context: The practice of component interface testing can be used to check the handling of data passed between various units, or subsystem components, beyond full integration testing between those units. The data being passed can be considered as "message packets" and the range or data types can be checked, for data generated from one unit, and tested for validity before being passed into another unit. One option for interface testing is to keep a separate log file of data items being passed, often with a timestamp logged to allow analysis of thousands of cases of data passed between units for days or weeks. Tests can include checking the handling of some extreme data values while other interface variables are passed as normal values. Unusual data values in an interface can help explain unexpected performance in the next unit. Component interface testing is a variation of black-box testing, with the focus on the data values beyond just the related actions of a subsystem component.

qas: question: What is the term used to test software during a pre-release?
answers: text: Operational Acceptance
is_impossible: no

question: What does Operational Acceptance focus on?
answers: text: operational readiness of the system
is_impossible: no

question: What is Operational Acceptance limited to while testing?
answers: text: limited to those tests which are required to verify the non-functional aspects of the system
is_impossible: no

question: What is Occupational Acceptance used for?
is_impossible: yes

question: What is an uncommon type of functional software testing?
is_impossible: yes

question: What is Operational Acceptance limited to while running?
is_impossible: yes

question: OAT focuses the least on what?
is_impossible: yes

question: When is the distinction between black and grey box not important?
is_impossible: yes

question: To whom is the beta testing released to?
is_impossible: yes

question: What method is used to test firmware under a specific load?
is_impossible: yes
context: Operational Acceptance is used to conduct operational readiness (pre-release) of a product, service or system as part of a quality management system. OAT is a common type of non-functional software testing, used mainly in software development and software maintenance projects. This type of testing focuses on the operational readiness of the system to be supported, and/or to become part of the production environment. Hence, it is also known as operational readiness testing (ORT) or Operations readiness and assurance (OR&A) testing. Functional testing within OAT is limited to those tests which are required to verify the non-functional aspects of the system.

qas: question: What is the most common reason for software failure?
answers: text: compatibility with other application software
is_impossible: no

question: What do developers commonly do when creating software that can lead to failures?
answers: text: lack of backward compatibility
is_impossible: no

question: What is the most common cause for software failure?
answers: text: lack of its compatibility with other application software
is_impossible: no

question: What often lacks in software developed when its released that can eventually lead to errors?
answers: text: a lack of backward compatibility
is_impossible: no

question: What does backwards compatibility always seem to be the cause of errors and bugs after a release?
answers: text: test software only on the latest version of the target environment
is_impossible: no

question: Lack of compatibility with other application software is an uncommon cause of what?
is_impossible: yes

question: Programmers develop software on the earliest version of what environment?
is_impossible: yes

question: What is the most uncommon reason for software failure?
is_impossible: yes

question: Target environments rarely differ greatly from the what?
is_impossible: yes

question: With several certifications out there that can be aquired, what is the one trait they all share?
is_impossible: yes

question: "Coverage" is referring to combined coverage but not what?
is_impossible: yes

question: What is the term for the public test that continues for a definite amount of time?
is_impossible: yes
context: A common cause of software failure (real or perceived) is a lack of its compatibility with other application software, operating systems (or operating system versions, old or new), or target environments that differ greatly from the original (such as a terminal or GUI application intended to be run on the desktop now being required to become a web application, which must render in a web browser). For example, in the case of a lack of backward compatibility, this can occur because the programmers develop and test software only on the latest version of the target environment, which not all users may be running. This results in the unintended consequence that the latest work may not function on earlier versions of the target environment, or on older hardware that earlier versions of the target environment was capable of using. Sometimes such issues can be fixed by proactively abstracting operating system functionality into a separate program module or library.

qas: question: Finding defects once a change in code had already happened is called?
answers: text: Regression testing
is_impossible: no

question: What happens to software after a major change in code that leads to regression??
answers: text: stops working as intended
is_impossible: no

question: What is a common method used during regression testing?
answers: text: re-running previous sets of test-cases
is_impossible: no

question: What determines how deep a tester will go during regression?
answers: text: phase in the release process and the risk of the added features
is_impossible: no

question: If changes need to occur during the softwares early release with regression testing how much of an impact does this have on the team as related to other testing? 
answers: text: typically the largest test effort in commercial software development
is_impossible: no

question: What type of testing is used to find defects after minor code changes?
is_impossible: yes

question: How does regression testing classify recovering software regressions?
is_impossible: yes

question: Usually regressions happen as an intended consequence of what?
is_impossible: yes

question: What are common methods of regression coding?
is_impossible: yes

question: What is usually the largest test effort in personal software development?
is_impossible: yes

question: Why are alpha version made available to the public?
is_impossible: yes

question: The tester chooses outputs to accomplish what?
is_impossible: yes

question: What three components make up Bottom Down Testing?
is_impossible: yes
context: Regression testing focuses on finding defects after a major code change has occurred. Specifically, it seeks to uncover software regressions, as degraded or lost features, including old bugs that have come back. Such regressions occur whenever software functionality that was previously working correctly, stops working as intended. Typically, regressions occur as an unintended consequence of program changes, when the newly developed part of the software collides with the previously existing code. Common methods of regression testing include re-running previous sets of test-cases and checking whether previously fixed faults have re-emerged. The depth of testing depends on the phase in the release process and the risk of the added features. They can either be complete, for changes added late in the release or deemed to be risky, or be very shallow, consisting of positive tests on each feature, if the changes are early in the release or deemed to be of low risk. Regression testing is typically the largest test effort in commercial software development, due to checking numerous details in prior software features, and even new software can be developed while using some old test-cases to test parts of the new design to ensure prior functionality is still supported.

qas: question: What typically comes after the Alpha stage in the development and testing of software?
answers: text: Beta testing
is_impossible: no

question: To whom is the beta testing released to?
answers: text: limited audience outside of the programming
is_impossible: no

question: What is it called when a public test continues indefinitely?
answers: text: perpetual beta
is_impossible: no

question: What type of testing comes before alpha testing?
is_impossible: yes

question: Beta versions are released to a broad audience known as what?
is_impossible: yes

question: Why are alpha version made available to the public?
is_impossible: yes

question: What is the term for the public test that continues for a definite amount of time?
is_impossible: yes

question: What are commonly used techniques during dynamic testing?
is_impossible: yes

question: What does grey-box testing involve?
is_impossible: yes

question: If the number of states is unknown, what group does this fall into?
is_impossible: yes
context: Beta testing comes after alpha testing and can be considered a form of external user acceptance testing. Versions of the software, known as beta versions, are released to a limited audience outside of the programming team known as beta testers. The software is released to groups of people so that further testing can ensure the product has few faults or bugs. Beta versions can be made available to the open public to increase the feedback field to a maximal number of future users and to deliver value earlier, for an extended or even indefinite period of time (perpetual beta).[citation needed]

qas: question: What method is used to cause a system to fail?
answers: text: Destructive testing
is_impossible: no

question: What does Destructive testing verify?
answers: text: software functions properly even when it receives invalid or unexpected inputs
is_impossible: no

question: What is one example of failure testing?
answers: text: Software fault injection
is_impossible: no

question: Destruction testing does what?
is_impossible: yes

question: What does destruction testing verify?
is_impossible: yes

question: What is an example of software fault injecture?
is_impossible: yes

question: There are very few open-source and free tools that do what?
is_impossible: yes

question: What makes up part of the SQA?
is_impossible: yes

question: With several certifications out there that can be aquired, what is the one trait they all share?
is_impossible: yes

question: Development Testing is designed by who?
is_impossible: yes
context: Destructive testing attempts to cause the software or a sub-system to fail. It verifies that the software functions properly even when it receives invalid or unexpected inputs, thereby establishing the robustness of input validation and error-management routines.[citation needed] Software fault injection, in the form of fuzzing, is an example of failure testing. Various commercial non-functional testing tools are linked from the software fault injection page; there are also numerous open-source and free software tools available that perform destructive testing.

qas: question: What method is used to test software under a specific load?
answers: text: Load testing
is_impossible: no

question: What two methods can be used when using Load Testing?
answers: text: data or a large number of users
is_impossible: no

question: What is called to test software functions when certain components increase in side?
answers: text: Volume testing
is_impossible: no

question: What is Stable testing also called?
answers: text: endurance testing
is_impossible: no

question: What method is used to test components under unexpected workloads?
answers: text: Stress testing
is_impossible: no

question: What method is used to test firmware under a specific load?
is_impossible: yes

question: What two methods cannot be used when using Load Testing?
is_impossible: yes

question: Volume Testing is a way to test firmware when?
is_impossible: yes

question: Testing reliability under expected or rare workload is called what?
is_impossible: yes

question: While looking for bug, what can testing not do?
is_impossible: yes

question: What is the secondary problem  with running software testing?
is_impossible: yes

question: What can a single defect not result in?
is_impossible: yes
context: Load testing is primarily concerned with testing that the system can continue to operate under a specific load, whether that be large quantities of data or a large number of users. This is generally referred to as software scalability. The related load testing activity of when performed as a non-functional activity is often referred to as endurance testing. Volume testing is a way to test software functions even when certain components (for example a file or database) increase radically in size. Stress testing is a way to test reliability under unexpected or rare workloads. Stability testing (often referred to as load or endurance testing) checks to see if the software can continuously function well in or above an acceptable period.

qas: question: What method is used that involves synchronization of a application?
answers: text: Development Testing
is_impossible: no

question: When is development testing used?
answers: text: construction phase of the software development lifecycle
is_impossible: no

question: What does Development testing look to eliminate?
answers: text: construction errors
is_impossible: no

question: What method is used that involved syncopation of an application?
is_impossible: yes

question: When is development testing not used?
is_impossible: yes

question: Development Testing attempts to eliminate instruction errors before code is promoted where?
is_impossible: yes

question: Development Testing is designed by who?
is_impossible: yes

question: When can dynamic testing occur?
is_impossible: yes

question: Which two old movements adhere to the "test-driven software development?"
is_impossible: yes

question: "Coverage" is referring to combined coverage but not what?
is_impossible: yes
context: Development Testing is a software development process that involves synchronized application of a broad spectrum of defect prevention and detection strategies in order to reduce software development risks, time, and costs. It is performed by the software developer or engineer during the construction phase of the software development lifecycle. Rather than replace traditional QA focuses, it augments it. Development Testing aims to eliminate construction errors before code is promoted to QA; this strategy is intended to increase the quality of the resulting software as well as the efficiency of the overall development and QA process.

qas: question: Which two current movements adhere to the "test-driven software development"?
answers: text: extreme programming and the agile software development
is_impossible: no

question: Under the development of agile software and extreme programing what is written first?
answers: text: unit tests are written first
is_impossible: no

question: What is the goal of Unit testing?
answers: text: achieve continuous integration where software updates can be published to the public frequently
is_impossible: no

question: Which two old movements adhere to the "test-driven software development?"
is_impossible: yes

question: Under the development of fragile software and extreme programming what is written first?
is_impossible: yes

question: The goal of unit testing is to achieve discontinuous integration where software updates can be what?
is_impossible: yes

question: What is the purpose of testing software?
is_impossible: yes

question: When the highest level components are tested first, the testing process is called what?
is_impossible: yes

question: What are commonly used techniques during dynamic testing?
is_impossible: yes
context: In contrast, some emerging software disciplines such as extreme programming and the agile software development movement, adhere to a "test-driven software development" model. In this process, unit tests are written first, by the software engineers (often with pair programming in the extreme programming methodology). Of course these tests fail initially; as they are expected to. Then as code is written it passes incrementally larger portions of the test suites. The test suites are continuously updated as new failure conditions and corner cases are discovered, and they are integrated with any regression tests that are developed. Unit tests are maintained along with the rest of the software source code and generally integrated into the build process (with inherently interactive tests being relegated to a partially manual build acceptance process). The ultimate goal of this test process is to achieve continuous integration where software updates can be published to the public frequently.  

qas: question: What three components make up Bottom Up Testing?
answers: text: modules, procedures, and functions
is_impossible: no

question: Bottom Up Testing helps facilitate the testing of what?
answers: text: the testing of higher level components
is_impossible: no

question: What does Bottom Up Testing also help with once the process has been repeated over and over again at all levels?
answers: text: makes it easier to report testing progress in the form of a percentage
is_impossible: no

question: When the highest level components are tested first, the testing process is called what?
is_impossible: yes

question: What three components make up Bottom Down Testing?
is_impossible: yes

question: This approach only works when half of the modules of the same what are ready?
is_impossible: yes

question: Bottom Up Testing helps determine levels of software developed and makes it harder to complete what?
is_impossible: yes

question: It has been disproved that each class is included into what?
is_impossible: yes

question: When is the distinction between black and grey box not important?
is_impossible: yes

question: This approach only works when half of the modules of the same what are ready?
is_impossible: yes
context: Bottom Up Testing is an approach to integrated testing where the lowest level components (modules, procedures, and functions) are tested first, then integrated and used to facilitate the testing of higher level components. After the integration testing of lower level integrated modules, the next level of modules will be formed and can be used for integration testing. The process is repeated until the components at the top of the hierarchy are tested. This approach is helpful only when all or most of the modules of the same development level are ready.[citation needed] This method also helps to determine the levels of software developed and makes it easier to report testing progress in the form of a percentage.[citation needed]

qas: question: If the number of states is unknown, what group does this fall into?
answers: text: Class II
is_impossible: no

question: There are three classes, what has been concluded and proven for all classes?
answers: text: each class is strictly included into the next
is_impossible: no

question: If the number of states are unknown and the finite state of the machine is failing for a single trace, which group does this fall into?
answers: text: Class III
is_impossible: no

question: It has been disproved that each class is included into what?
is_impossible: yes

question: If there are infinite sets of inputs and outputs, the states belong to what class?
is_impossible: yes

question: The inclusion into Class I requires what?
is_impossible: yes

question: Matthew Hennessy wrote what?
is_impossible: yes

question: When is the distinction between black and grey box not important?
is_impossible: yes

question: When is the distinction between black and grey box not important?
is_impossible: yes

question: Why are alpha version made available to the public?
is_impossible: yes
context: It has been proved that each class is strictly included into the next. For instance, testing when we assume that the behavior of the implementation under test can be denoted by a deterministic finite-state machine for some known finite sets of inputs and outputs and with some known number of states belongs to Class I (and all subsequent classes). However, if the number of states is not known, then it only belongs to all classes from Class II on. If the implementation under test must be a deterministic finite-state machine failing the specification for a single trace (and its continuations), and its number of states is unknown, then it only belongs to classes from Class III on. Testing temporal machines where transitions are triggered if inputs are produced within some real-bounded interval only belongs to classes from Class IV on, whereas testing many non-deterministic systems only belongs to Class V (but not all, and some even belong to Class I). The inclusion into Class I does not require the simplicity of the assumed computation model, as some testing cases involving implementations written in any programming language, and testing implementations defined as machines depending on continuous magnitudes, have been proved to be in Class I. Other elaborated cases, such as the testing framework by Matthew Hennessy under must semantics, and temporal machines with rational timeouts, belong to Class II.

qas: question: With several certifications out there that can be aquired, what is the one trait they all share?
answers: text: requires the applicant to show their ability to test software
is_impossible: no

question: What has the inability for the applicant to show how well they test led to?
answers: text: testing field is not ready for certification
is_impossible: no

question: What four traits can a certification not measure?
answers: text: individual's productivity, their skill, or practical knowledge
is_impossible: no

question: What programs are available to support non-professional aspirations of software testers?
is_impossible: yes

question: What certification requires applicants to demonstrate ability?
is_impossible: yes

question: Some say the testing field is ready for what?
is_impossible: yes

question: Certification is a measure of what?
is_impossible: yes

question: What is one example of failure testing?
is_impossible: yes

question: Why are alpha version made available to the public?
is_impossible: yes

question: What does specialization-based testing aim to test?
is_impossible: yes
context: Several certification programs exist to support the professional aspirations of software testers and quality assurance specialists. No certification now offered actually requires the applicant to show their ability to test software. No certification is based on a widely accepted body of knowledge. This has led some to declare that the testing field is not ready for certification. Certification itself cannot measure an individual's productivity, their skill, or practical knowledge, and cannot guarantee their competence, or professionalism as a tester.

qas: question: What makes up part of the SQA?
answers: text: Software testing
is_impossible: no

question: What is the primary concern for the software specialist and auditors?
answers: text: software development process
is_impossible: no

question: What type of software would have a better defect tolerance?
answers: text: video game
is_impossible: no

question: What does grey-box testing involve?
is_impossible: yes

question: There are few approached in what type of testing?
is_impossible: yes

question: Test cases are built around specializations and what else?
is_impossible: yes
context: Software testing is a part of the software quality assurance (SQA) process.:347 In SQA, software process specialists and auditors are concerned for the software development process rather than just the artifacts such as documentation, code and systems. They examine and change the software engineering process itself to reduce the number of faults that end up in the delivered software: the so-called "defect rate". What constitutes an "acceptable defect rate" depends on the nature of the software; A flight simulator video game would have much higher defect tolerance than software for an actual airplane. Although there are close links with SQA, testing departments often exist independently, and there may be no SQA function in some companies.[citation needed]