Types of Testing
Risk Based Execution
JIRA
Types of Testing 2
Release Management
100

Type of testing that is preformed in ensure the application is doing exactly what is expected

What is positive testing

100

The location where risk statements are created and stored

What is a test library

100

A defect found while testing code that has not elevated to production on a specific user story you are testing.

What is a WIP defect

100

Testing where test cases are not created in advance but testers check system on the fly.

What is exploratory testing

100

This field in JIRA identifies when changes move to production

What is a fix version

200

Testing that is done to confirm the test environments as a whole is ready for the release

What is release regression

200

This is used to track scope, risks, approach, entry and exist criteria

What is a test plan

200

This label is used when a defect is identified in the lower environment and converted to a production defect

What is Converted_LE_Defect

200

Testing to confirm that a code deploys has not affected existing code

What is regression testing

200

This definition means code has moved to production

What is deploy

300
Testing that is done specific to an area of focus

What is targeted testing

300

This is designed to display gadgets that help you organize your projects, assignments and progress

What is a dashboard

300

This field is used in defects to identify which environment your defect was found

what is PL Environment

300

Testing that evaluates the entire application flow, from start to finish

What is end to end testing

300

During this time period we restrict code changes to the applications 

what is code freeze 

400

Testing that is done to confirm the feature as a whole is ready for the release

What is feature regression testing

400

This process should be used when a new feature is implemented in production and a new risk statement is identified

What is the scoring approval 

400

An error in coding which causes incorrect or unexpected results that do not meet the requirement


What is a defect
400

Testing that behaves as expected with the negative or unwanted inputs

what is negative testing

400

This definition means we are live and functionality is available to our stakeholders

what is release

500

Validation that is done in production after a defect or feature elevates

What is production validation

500

This is assessing the risk on the code complexity, business criticality, and frequency within our applications. 

What is risk based testing

500

This label is used when lower environments are down and or blocked all testing and multiple users

what is TestingBlocker

500

Testing when we need to validate functionality that has parameters (dates, number ranges, factor testing)

What is edge case testing

500
This field is used when a feature is deploying but not releasing

What is the release note detail section

M
e
n
u