romikgosai/squad_modified huggingface dataset:
Most common are historical works where the protagonist is either a samurai or former samurai (or another rank or position) who possesses considerable martial skill. Eiji Yoshikawa is one of the most famous Japanese historical novelists. His retellings of popular works, including Taiko, Musashi and Heike Tale, are popular among readers for their epic narratives and rich realism in depicting samurai and warrior culture.[citation needed] The samurai have also appeared frequently in Japanese comics (manga) and animation (anime). Samurai-like characters are not just restricted to historical settings and a number of works set in the modern age, and even the future, include characters who live, train and fight like samurai. Examples are Samurai Champloo, Requiem from the Darkness, Muramasa: The Demon Blade, and Afro Samurai. Some of these works have made their way to the west, where it has been increasing in popularity with America.

Questions and answers:
['
Q: Who is Eiji Yoshikawa?
A: one of the most famous Japanese historical novelists', "
Q: Why are Eiji Yoshikawa's books popular?
A: for their epic narratives and rich realism in depicting samurai and warrior culture", '
Q: What are Japanese comic books called?
A: manga', '
Q: What are Japanese animation called?
A: anime']
Just in the last two decades,[when?] samurai have become more popular in America. “Hyperbolizing the samurai in such a way that they appear as a whole to be a loyal body of master warriors provides international interest in certain characters due to admirable traits” (Moscardi, N.D.). Through various medium, producers and writers have been capitalizing on the notion that Americans admire the samurai lifestyle. The animated series, Afro Samurai, became well-liked in American popular culture due to its blend of hack-and-slash animation and gritty urban music.

Questions and answers:
['
Q: Who said America hyperbolizes the samurai?
A: Moscardi, N.D.', '
Q: What kind of animation did Afro Samurai have?
A: hack-and-slash', '
Q: What kind of music did Afro Samurai have?
A: gritty urban']
Created by Takashi Okazaki, Afro Samurai was initially a doujinshi, or manga series, which was then made into an animated series by Studio Gonzo. In 2007 the animated series debuted on American cable television on the Spike TV channel (Denison, 2010). The series was produced for American viewers which “embodies the trend... comparing hip-hop artists to samurai warriors, an image some rappers claim for themselves (Solomon, 2009). The storyline keeps in tone with the perception of a samurais finding vengeance against someone who has wronged him. Starring the voice of well known American actor Samuel L. Jackson, “Afro is the second-strongest fighter in a futuristic, yet, still feudal Japan and seeks revenge upon the gunman who killed his father” (King 2008). Due to its popularity, Afro Samurai was adopted into a full feature animated film and also became titles on gaming consoles such as the PlayStation 3 and Xbox. Not only has the samurai culture been adopted into animation and video games, it can also be seen in comic books.

Questions and answers:
['
Q: Who created Afro Samurai?
A: Takashi Okazaki', '
Q: Who made Afro Samurai into an animated TV show?
A: Studio Gonzo', '
Q: When did Afro Samurai first air?
A: 2007', '
Q: On what channel did Afro Samurai air?
A: Spike TV', '
Q: Who was the star voice actor of Afro Samurai?
A: Samuel L. Jackson']
American comic books have adopted the character type for stories of their own like the mutant-villain Silver Samurai of Marvel Comics. The design of this character preserves the samurai appearance; the villain is “Clad in traditional gleaming samurai armor and wielding an energy charged katana” (Buxton, 2013). Not only does the Silver Samurai make over 350 comic book appearances, the character is playable in several video games, such as Marvel Vs. Capcom 1 and 2. In 2013, the samurai villain was depicted in James Mangold’s film The Wolverine. Ten years before the Wolverine debuted, another film helped pave the way to ensure the samurai were made known to American cinema: A film released in 2003 titled The Last Samurai, starring Tom Cruise, is inspired by the samurai way of life. In the film, Cruise’s character finds himself deeply immersed in samurai culture. The character in the film, “Nathan Algren, is a fictional contrivance to make nineteenth-century Japanese history less foreign to American viewers”.(Ravina, 2010) After being captured by a group of samurai rebels, he becomes empathetic towards the cause they fight for. Taking place during the Meiji Period, Tom Cruise plays the role of US Army Captain Nathan Algren, who travels to Japan to train a rookie army in fighting off samurai rebel groups. Becoming a product of his environment, Algren joins the samurai clan in an attempt to rescue a captured samurai leader. “By the end of the film, he has clearly taken on many of the samurai traits, such as zen-like mastery of the sword, and a budding understanding of spirituality”. (Manion, 2006)

Questions and answers:
["
Q: In what company's comics did Silver Samurai appear?
A: Marvel", "
Q: What is Silver Samurai's weapon?
A: an energy charged katana", '
Q: How many comic books has Silver Samurai appeared in?
A: over 350', '
Q: Who starred in The Last Samurai?
A: Tom Cruise', '
Q: Who did Tom Cruise play in The Last Samurai?
A: US Army Captain Nathan Algren']
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.

Questions and answers:
['
Q: What is the purpose of testing software?
A: finding software bugs', '
Q: Why is it so difficult to locate bugs in software?
A: tests for even simple software components is practically infinite', '
Q: What can come from one bug being fixed?
A: it can illuminate other, deeper bugs,']
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.

Questions and answers:
['
Q: What can testing not completely find?
A: all the defects', '
Q: While looking for bugs, what else can testing do?
A: furnishes a criticism or comparison', '
Q: What does the software compare during testing against?
A: oracles—principles or mechanisms', '
Q: What make up the oracle during testing?
A: specifications, contracts, comparable products, past versions']
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.

Questions and answers:
['
Q: What is the primamry reason for testing software?
A: to detect software failures', '
Q: What can testing software not fully completely establish?
A: cannot establish that a product functions properly under all conditions', '
Q: What does the scope of testing the software also look at?
A: examination of code as well as execution of that code', '
Q: Which two teams would you normally separate when writing and testing software?
A: testing organization may be separate from the development team']
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.

Questions and answers:
['
Q: What is the first step that leads to a software failure?
A: programmer makes an error', '
Q: What is the result of the programmer making a mistake?
A: defect (fault, bug)', '
Q: When can software defects in dead code cause problems?
A: run on a new computer hardware platform']
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.

Questions and answers:
['
Q: What is the primary issue with running software testing?
A: testing under all combinations of inputs and preconditions (initial state) is not feasible', '
Q: What types of software bugs are difficult to find during testing?
A: defects that occur infrequently', '
Q: What other non-functional dimensions can cause software to underperform and cause other problems?
A: usability, scalability, performance, compatibility, reliability']
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.

Questions and answers:
['
Q: Although software developers are unable to test everything, what do they run to keep the testing to a minimum? 
A: use combinatorial test design', '
Q: What does the use of combinatorial testing consist of?
A: get greater test coverage with fewer tests', '
Q: What two types of testing are involved with combinatorial testing as mentioned here?
A: speed or test depth']
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.

Questions and answers:
['
Q: What determines the cost of fixing a bug?
A: the earlier a defect is found', "
Q: Ho many more times would the cost be if the problem is found after the software's release?
A: 10–100 times more", '
Q: What could possibly lessen the cost of fixing buggy software?
A: cloud-based services']
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.

Questions and answers:
['
Q: Name three approaches software testers take when testing their software?
A: Reviews, walkthroughs, or inspections', '
Q: What is the term that is used to described executing programmed code with a given set of test?
A: dynamic testing', '
Q: When can dynamic testing occur?
A: before the program is 100% complete', '
Q: What are commonly used techniques during dynamic testing?
A: stubs/drivers or execution from a debugger environment']
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).

Questions and answers:
['
Q: What is another term used for White-box testing?
A: clear box testing', '
Q: What is involved with White-box testing?
A: by seeing the source code', '
Q: Which two procedures are used to design test cases in White-box testing?
A: testing an internal perspective of the system, as well as programming skills']
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.

Questions and answers:
['
Q: What is the main difference between black-box testing and white-box testing?
A: seeing the source code', '
Q: What are the software testers aware of?
A: aware of what the software is supposed to do', '
Q: What are the first three methods mentioned that make up black-box testing??
A: equivalence partitioning, boundary value analysis']
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.

Questions and answers:
['
Q: What term is used to test functionality of the software accordingly with the application requirements?
A: Specification-based testing', '
Q: What are the test cases built around?
A: specifications and requirements', '
Q: When building test cases which of the two methods used is more common over the other?
A: functional']
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.

Questions and answers:
['
Q: What is one huge advantage to using the black-box method?
A: no programming knowledge is required', '
Q: What can black-box testing sometimes be referred to with the in-ability to see the code?
A: like a walk in a dark labyrinth without a flashlight.', '
Q: What is a good reason to have testers and developers separate?
A: tester likely has a different set and may emphasize different areas of functionality']
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.

Questions and answers:
['
Q: What does grey-box testing involve?
A: having knowledge of internal data structures and algorithms', "
Q: What does a grey-box tester not need to run their test?
A: not required to have full access to the software's source code", '
Q: What does not qualify as grey-box testing?
A: Manipulating input data and formatting output']
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.

Questions and answers:
['
Q: What does a grey-box tester implement when they have limited information?
A: intelligent test scenarios', '
Q: What dopes a typical grey-box tester sets up?
A: an isolated testing environment', '
Q: What does the tester execute while performing certain actions?
A: SQL statements']
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.

Questions and answers:
['
Q: What are the four recognized levels of testing software?
A: unit testing, integration testing, component interface testing, and system testing', '
Q: What are these test (level testing) typically grouped by?
A: software development process, or by the level of specificity of the test', '
Q: What is defined in the SWEBOK guide as to testing the main levels?
A: unit-, integration-, and system testing', '
Q: What are the other levels classified by?
A: the testing objective']
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.

Questions and answers:
['
Q: What is the main reasoning behind Unit testing that involves synchronization of the application on a broad spectrum? 
A: reduce software development risks, time, and costs', '
Q: Who performs the Unit testing phase?
A: software developer or engineer', '
Q: What does Unit testing look to eliminate?
A: construction errors', '
Q: By elimination construction errors, what is the expected end result?
A: increase the quality of the resulting software']
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.

Questions and answers:
['
Q: What is it called to check data passed between units?
A: component interface testing', '
Q: What is it called when data is being passed?
A: message packets', '
Q: What is an option  of component interface testing  used while sending message packets?
A: keep a separate log file of data items being passed', '
Q: What is a variation of black-box testing?
A: Component interface testing']
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.

Questions and answers:
['
Q: What is the term used to test software during a pre-release?
A: Operational Acceptance', '
Q: What does Operational Acceptance focus on?
A: operational readiness of the system', '
Q: What is Operational Acceptance limited to while testing?
A: limited to those tests which are required to verify the non-functional aspects of the system']