Key Terms

Question 1

Requirements

Answer 1

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.

Question 2

Business Requirements

Answer 2

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.

Question 3

User Requirement

Answer 3

These requirements are gathered using use cases, user scenarios, and user
stories and are documented in a user requirement document format (User
Story)

Question 4

System Requirements

Answer 4

incorporated in a software product to make it perform and function in a
specific manner to achieve its target and goal.

Question 5

Use Case

Answer 5

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

Question 6

User Story

Answer 6

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].”

Question 7

Test Plan

Answer 7

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.

Question 8

Test Strategy

Answer 8

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.

Question 9

Requirement Traceability Matrix

Answer 9

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.

Question 10

Test Scenario

Answer 10

Scenario testing is a software testing activity that uses scenarios: hypothetical stories to
help the tester work through a complex problem or test system

Question 11

Test Cases

Answer 11

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.

Question 12

Test Scripts

Answer 12

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.

Question 13

Test Steps

Answer 13

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.

Question 14

Defect Bug

Answer 14

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.

Question 15

Definition of Done

Answer 15

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

Question 16

GUI

Answer 16

A graphical user interface (GUI) is a type of user interface through which users interact with
electronic devices via visual indicator representations.

Question 17

AUT

Answer 17

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”.

Question 18

Test Data

Answer 18

Any data used during testing Real data,
fake/dummy data

Question 19

Demo

Answer 19

Is to demonstrate or a presentation of any
work completed before going live

Question 20

Showstopper

Answer 20

A bug the prevents you from any
further testing

Question 21

Hotfix

Answer 21

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

Question 22

Critical Priority

Answer 22

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

Question 23

Severity

Answer 23

How dangerous a bug is rated Low - Minor - Major - Critical

Question 24

Artifacts

Answer 24

It’s anything that is created so a piece of software can be developed. This might include
things like data models, diagrams, setup scripts

Question 25

ETL - Extract Transform Load

Answer 25

These are three database functions that are combined into one tool to extract data from a
database, modify it, and place it into another database

Question 26

CI & CD - Continuous Intergration, Continous
Development

Answer 26

CI and CD stand for continuous integration and continuous delivery/continuous deployment. In very simple terms, CI is a modern software development practice in which incremental code changes are made frequently and reliably. … The code is then delivered quickly and seamlessly as
a part of the CD process

Question 27

Devops

Answer 27

DevOps is a set of practices that combines software development (Dev) and IT operations
(Ops).It aims to shorten the systems development life cycle and provide continuous delivery with high software quality.

Question 28

Git

Answer 28

Git - Git Hub is a Collaboration platform. It is built on top of
git. It allows you to keep both local and remote copies of
your project. A project which you can publish it among
your team members as they can use it and update it from
there itself. Git is a version control system that lets
you manage and keep track of your source code history

Question 29

Github

Answer 29

a Collaboration platform. Github is a web-based platform
used for version control. Git simplifies the process of
working with other people and makes it easy to collaborate
on projects. Team members can work on files and easily
merge their changes in with the master branch of the
project. GitHub is a cloud-based hosting service that lets
you manage Git repositories. If you have open-source
projects that use Git, then GitHub is designed to help you
better manage them

Question 30

Repository

Answer 30

A software repository, or “repo” for short, is a storage location
for software packages. Often a table of contents is also
stored, along with metadata. A software repository is
typically managed by source control or repository managers.
Software repositories serve the general purpose of
promoting collaborative use by offering remote access to
code modules and software packages. A software repository
is also known as a code repository

Question 31

Pipeline

Answer 31

A delivery pipeline is a set of processes that can be automated to compile and build and
deploy code to production as efficiently as possible. It is also known as a software delivery
pipeline or continuous delivery pipeline. This pipeline needs to be optimized from end to
end

Question 32

Release

Answer 32

A release note refers to the technical documentation produced and distributed alongside
the launch of a new software product or a product update (e.g., recent changes, feature
enhancements, or bug fixes). It very briefly describes a new product or succinctly details
specific changes included in a
product update

Question 33

Business Requirement Document

Answer 33

A business requirements document (BRD), is a formal report that details all the objectives
or “requirements” for a new project, program or business solution. It describes a business
need or objective along with what is expected as the project proceeds.

Question 34

Technical Requirement Document

Answer 34

A technical requirement document, also known as a product requirement document,
defines the functionality, features, and purpose of a product that you’re going

Question 35

Software Requirement Specification

Answer 35

A software requirements specification (SRS) is a document that describes what the
software will do and how it will be expected to perform. It also describes the functionality
the product needs to fulfill all stakeholders (business, users) needs.

Question 36

Detail Design Document

Answer 36

The detailed design document formally records the design of the content — that is, the
lessons or modules and all the deliverables necessary. The detailed design document
records the design of content

Question 37

Requirement Traceability Matrix

Answer 37

A requirements traceability matrix is a document that demonstrates the relationship
between requirements and other artifacts. It’s used to prove that requirements have been
fulfilled. And it typically documents requirements, tests, test results, and issues

Question 38

SDLC

Answer 38

Software Development Life Cycle (SDLC), providing bug and defect free
software and making sure it is built to our clients’ needs and expectations

Question 39

STLC

Answer 39

Software Testing Life Cycle (STLC) is a sequence of specific activities conducted during
the testing process to ensure software quality goals are met. STLC involves both
verification and validation activities. Contrary to popular belief, Software Testing is not
just a single/isolate activity, i.e. testing. It consists of a series of activities carried out
methodologically to help certify your software product. STLC stands for Software
Testing Life Cycle.

Question 40

Functional (System)

Answer 40

Define and describes the functions to be performed, and features to be possessed by a software.

Question 41

Non-Functional (system)

Answer 41

Used to evaluate and assess the software product behavior under unexpected conditoins and enviornment