Key Terms Flashcards
Requirements
What the clients want the system to do. A Primary requirement needed in
the development of a software product specifically for a targeted group or
audience and the specific environment.
Business Requirements
These requirements outline a general overview of a product such as it’s
primary use, why it is needed, its scope & vision, what business benefits will
be gain, intended audience or users etc.
User Requirement
These requirements are gathered using use cases, user scenarios, and user
stories and are documented in a user requirement document format (User
Story)
System Requirements
incorporated in a software product to make it perform and function in a
specific manner to achieve its target and goal.
Use Case
A use case is a description of the ways in which a user interacts with a system or
product. A use case may establish the success scenarios, the failure scenarios,
and any critical variations or exceptions. A use case can be written or made
visual with the help of a use case model tool. The BA usually creates this
document
User Story
A user story is an informal, general explanation of a software feature written from the perspective of the end user or customer. User stories are often expressed in a simple sentence,
structured as follows:
“As a [persona], I [want to], [so that].”
Test Plan
A test plan includes a product description, objectives, testing strategies, scope, schedule,
procedures, testing resources, and deliverables. Test plans are essential in the development
of software as they outline what testing needs doing to ensure the software is up to
standard and is working exactly how it
should.
Test Strategy
A Test Strategy is a plan for defining an approach to the Software Testing Life Cycle (STLC).
It guides QA teams to define Test Coverage and testing scope. It helps testers get a clear
picture of the project at any instance. The possibility of missing any test activity is very low
when there is a proper test strategy in place.
Requirement Traceability Matrix
A Traceability Matrix is a document that co-relates any two-baseline documents that
require a manyto- many relationship to check the completeness of the relationship. It is
used to track the requirements and to check the current project requirements are met.
Test Scenario
Scenario testing is a software testing activity that uses scenarios: hypothetical stories to
help the tester work through a complex problem or test system
Test Cases
A TEST CASE is a set of actions executed to verify a particular feature or functionality of your
software application. A Test Case contains test steps, test data, precondition, postcondition
developed for specific test scenarios to verify any requirement.
The test case includes specific variables or conditions, using which a testing engineer can
compare expected and actual results to determine whether a software product is functioning as per the requirements of the customer.
Test Scripts
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.
Test Steps
Test Steps describe the execution steps and expected results that are
documented against each one of those steps. Each step is marked pass or fail
based on the comparison result between the expected and actual outcome.
Defect Bug
In software testing, a bug is the informal name of defects, which means that
software or application is not working as per the requirement. When we have
some coding error, it leads a program to its breakdown, which is known as a
bug.
Definition of Done
The definition of done (DoD) is when all conditions, or acceptance criteria, that a software
product must satisfy are met and ready to be accepted by a user, customer, team, or consuming system. … It lowers rework, by preventing user stories that don’t meet the definition
from being promoted to higher level environments
GUI
A graphical user interface (GUI) is a type of user interface through which users interact with
electronic devices via visual indicator representations.
AUT
AUT is “Application under test”. After the designing and coding section of the development
cycle,when the application(build) comes under testing then at that time application state
is under test,so at that time period that application(build) is called “Application under test”.
Test Data
Any data used during testing Real data,
fake/dummy data
Demo
Is to demonstrate or a presentation of any
work completed before going live
Showstopper
A bug the prevents you from any
further testing
Hotfix
A hotfix, is a software patch that is applied to “hot” (aka live) systems. For us developers, this
usually means that it’s a change that was made quickly and outside of the normal development processes, as an urgent measure against certain issues that need to be fix immediately
Critical Priority
Priority is how quickly a bug should be fixed and eradicated from the website. Bug priority
indicates the sense of urgency for dealing with a bug on our website. Low - Medium- High
Severity
How dangerous a bug is rated Low - Minor - Major - Critical
Artifacts
It’s anything that is created so a piece of software can be developed. This might include
things like data models, diagrams, setup scripts
