|
Scenario Testing
Scenario testing is a software testing activity that uses scenarios: hypothetical stories to help the tester work through a complex problem or test system. The ideal scenario test is a credible, complex, compelling or motivating story; the outcome of which is easy to evaluate. These tests are usually different from test cases in that test cases are single steps whereas scenarios cover a number of steps. History Cem Kaner coined the phrase scenario test by October 2003. He commented that one of the most difficult aspects of testing was maintaining step-by-step test cases along with their expected results. His paper attempted to find a way to reduce the re-work of complicated written tests and incorporate the ease of use cases. A few months later, Hans Buwalda wrote about a similar approach he had been using that he called "soap opera testing". Like television soap operas these tests were both exaggerated in activity and condensed in time. The key to both approaches was to avoid st ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Software Testing
Software testing is the act of checking whether software satisfies expectations. Software testing can provide objective, independent information about the Quality (business), quality of software and the risk of its failure to a User (computing), user or sponsor. Software testing can determine the Correctness (computer science), correctness of software for specific Scenario (computing), scenarios but cannot determine correctness for all scenarios. It cannot find all software bug, bugs. Based on the criteria for measuring correctness from an test oracle, oracle, software testing employs principles and mechanisms that might recognize a problem. Examples of oracles include specifications, Design by Contract, contracts, comparable products, past versions of the same product, inferences about intended or expected purpose, user or customer expectations, relevant standards, and applicable laws. Software testing is often dynamic in nature; running the software to verify actual output ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Scenario (computing)
In computing, a scenario (, ; loaned (), ) is a narrative of foreseeable interactions of user roles (known in the Unified Modeling Language as 'actors') and the technical system, which usually includes computer hardware and software. A scenario has a goal, which is usually functional. A scenario describes one way that a system is used, or is envisaged to be used, in the context of an activity in a defined time-frame. The time-frame for a scenario could be (for example) a single transaction; a business operation; a day or other period; or the whole operational life of a system. Similarly the scope of a scenario could be (for example) a single system or a piece of equipment; an equipped team or a department; or an entire organization. Scenarios are frequently used as part of the system development process. They are typically produced by usability or marketing specialists, often working in concert with end users and developers. Scenarios are written in plain language, with mini ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Test Case
In software engineering, a test case is a specification of the inputs, execution conditions, testing procedure, and expected results that define a single test to be executed to achieve a particular software testing objective, such as to exercise a particular program path or to verify compliance with a specific requirement. Test cases underlie testing that is methodical rather than haphazard. A battery of test cases can be built to produce the desired coverage of the software being tested. Formally defined test cases allow the same tests to be run repeatedly against successive versions of the software, allowing for effective and consistent regression testing. Formal test cases In order to fully test that all the requirements of an application are met, there must be at least two test cases for each requirement: one positive test and one negative test. If a requirement has sub-requirements, each sub-requirement must have at least two test cases. Keeping track of the link between ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Addison-Wesley
Addison–Wesley is an American publisher of textbooks and computer literature. It is an imprint of Pearson plc, a global publishing and education company. In addition to publishing books, Addison–Wesley also distributes its technical titles through the O'Reilly Online Learning e-reference service. Addison–Wesley's majority of sales derive from the United States (55%) and Europe (22%). The Addison–Wesley Professional Imprint produces content including books, eBooks, and video for the professional IT worker including developers, programmers, managers, system administrators. Classic titles include '' The Art of Computer Programming'', '' The C++ Programming Language'', '' The Mythical Man-Month'', and '' Design Patterns''. History Lew Addison Cummings and Melbourne Wesley Cummings founded Addison–Wesley in 1942, with the first book published by Addison–Wesley being Massachusetts Institute of Technology professor Francis Weston Sears' ''Mechanics''. Its first comput ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Cem Kaner
Cem Kaner is a professor of software engineering at Florida Institute of Technology, and the Director of Florida Tech's Center for Software Testing Education & Research (CSTER) since 2004. He is perhaps best known outside academia as an advocate of software usability and software testing. Prior to his professorship, Kaner worked in the software industry beginning in 1983 in Silicon Valley "as a tester, programmer, tech writer, software development manager, product development director, and independent software development consultant." In 1988, he and his co-authors Jack Falk and Hung Quoc Nguyen published what became, at the time, "the best selling book on software testing," ''Testing Computer Software''. See #Publications above for details on editions of ''Testing Computer Software.'' He has also worked as a user interface designer. In 2004 he cofounded the non-profit Association for Software Testing. Education Kaner received a Bachelor's Degree from Brock University in 197 ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Use Case
In both software and systems engineering, a use case is a structured description of a system’s behavior as it responds to requests from external actors, aiming to achieve a specific goal. It is used to define and validate functional requirements A use case is a list of actions or event steps typically defining the interactions between a role (known in the Unified Modeling Language (UML) as an ''actor'') and a system to achieve a goal. The actor can be a human or another external system. In systems engineering, use cases are used at a higher level than within software engineering, often representing missions or stakeholder goals. The detailed requirements may then be captured in the Systems Modeling Language (SysML) or as contractual statements. Differences between Systems and Software Engineering Use Cases In software engineering, the use case defines potential scenarios of the software in response to an external request (such as user input). In systems engineering, a use c ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Narrative Thread
A narrative thread, or plot thread (or, more ambiguously, a storyline), refers to particular elements and techniques of writing to center the story in the action or experience of characters rather than to relate a matter in a dry "all-knowing" sort of narration. Thus, the narrative threads experienced by different, but specific characters or sets of characters are those seen in the eyes of those characters that together form a plot element or subplot in the work of fiction. In this sense, each narrative thread is the narrative portion of a work that pertains to the world view of the participating characters cognizant of their piece of the whole, and they may be the villains, the protagonists, a supporting character, or a relatively disinterested official utilized by the author, each thread of which is woven together by the writer to create a work. By utilizing different threads, the writer enables the reader to get pieces of the overall plot while positioning them to identify wi ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Conceptual Model
The term conceptual model refers to any model that is formed after a wikt:concept#Noun, conceptualization or generalization process. Conceptual models are often abstractions of things in the real world, whether physical or social. Semantics, Semantic studies are relevant to various stages of process of concept formation, concept formation. Semantics is fundamentally a study of concepts, the meaning that thinking beings give to various elements of their experience. Overview Concept models and conceptual models The value of a conceptual model is usually directly proportional to how well it corresponds to a past, present, future, actual or potential state of affairs. A concept model (a model of a concept) is quite different because in order to be a good model it need not have this real world correspondence. In artificial intelligence, conceptual models and conceptual graphs are used for building expert systems and knowledge-based systems; here the analysts are concerned to repres ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Business Vertical
In microeconomics, management and international political economy, vertical integration, also referred to as vertical consolidation, is an arrangement in which the supply chain of a company is integrated and owned by that company. Usually each member of the supply chain produces a different product or (market-specific) service, and the products combine to satisfy a common need. It contrasts with horizontal integration, wherein a company produces several items that are related to one another. Vertical integration has also described management styles that bring large portions of the supply chain not only under a common ownership but also into one corporation (as in the 1920s when the Ford River Rouge complex began making much of its own steel rather than buying it from suppliers). Vertical integration can be desirable because it secures supplies needed by the firm to produce its product and the market needed to sell the product, but it can become undesirable when a firm's actions ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Test Script
A test script in software testing is a set of instructions that will be performed on the system under test to test that the system functions as expected. Types of test scripts There are various means for executing test scripts. These last two types are also done in manual testing. * Manual testing. These are more commonly called test cases. * Automated testing. ** Short program written in a programming language used to test part of the functionality of a software system. Test scripts written as a short program can either be written using a special automated functional GUI test tool (such as HP QuickTest Professional, Borland SilkTest, IBM TPNS and Rational Robot) or in a well-known programming language (such as C++, C#, Tcl, Expect, Java, PHP, Perl, Powershell, Python, or Ruby). As documented in IEEE, ISO and IEC. ** Extensively parameterized short programs a.k.a. Data-driven testing ** Reusable steps created in a table a.k.a. keyword-driven or table-driven testing. ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Test Suite
In software development, a test suite, less commonly known as a validation suite, is a collection of test cases that are intended to be used to test a software program to show that it has some specified set of behaviors. A test suite often contains detailed instructions or goals for each collection of test cases and information on the system configuration to be used during testing. A group of test cases may also contain prerequisite states or steps and descriptions of the following tests. Collections of test cases are sometimes termed a test plan, a test script, or even a test scenario. Types Occasionally, test suites are used to group similar test cases together. A system might have a smoke test suite that consists only of smoke tests or a test suite for some specific functionality in the system. It may also contain all tests and signify if a test should be used as a smoke test or for some specific functionality. In model-based testing, one distinguishes between ''abstract ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Session-based Testing
Session-based testing is a software test method that aims to combine accountability and exploratory testing to provide rapid defect discovery, creative on-the-fly test design, management control and metrics reporting. The method can also be used in conjunction with scenario testing. Session-based testing was developed in 2000 by Jonathan and James Marcus Bach. Session-based testing can be used to introduce measurement and control to an immature test process and can form a foundation for significant improvements in productivity and error detection. Session-based testing can offer benefits when formal requirements are not present, incomplete, or changing rapidly. Elements of session-based testing Mission The mission in Session Based Test Management identifies the purpose of the session, helping to focus the session while still allowing for exploration of the system under test. According to Jon Bach, one of the co-founders of the methodology, the mission explains "what we are te ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
