Qa

Front 1

TESTING

Back 1

Testing is a process of gathering information by observations and comparing them with the expectations

Front 2

SOFTWARE TESTING

Back 2

Software testing a process of verifying and validating whether the program is performing correctly without any bugs. also, It is the process of analyzing software for the purpose of finding bugs and fixing them

Front 3

Two basic types of software testing

Back 3

Manual and Automated testing. Tests which are suitable for manual testing are not necessarily suitable for test automation.
Time consuming Speed
Low reliability Repeatability(стабильнос)
Human resources Coverage
Inconsistent Reliability(надежность)
Reusability(Повтор использ)

Front 4

MANUAL TESTING

Back 4

This is considered to be one of the oldest type of software testing methods, in which test cases are designed and reviewed by the team, before executing it.

Front 5

AUTOMATED TESTING

Back 5

This software testing type applies automation in the testing, which can be applied to various parts of a software process such as test case management, executing test cases, defect management, reporting of the bugs/defects. AUTOMATION MUST BE REPEATED ACTION, BUT CAN BE SIMPLE

Front 6

Top-Down Integration Testing:

Back 6

This is totally opposite to bottom-up approach, as it tests the top level modules are tested and the branch of the module are tested step by step using 'Stubs' until the related module comes to an end.

Front 7

Bottom-Up Integration Testing:

Back 7

In this type of integration testing, the lowest level components are tested first and then alleviate the testing of higher level components using 'Drivers'.

Front 8

MUTATION TESTING

Back 8

In this type of software testing, the application is tested for the code that was modified after fixing a particular bug/defect

Front 9

SDLC

Back 9

The Software Development Life Cycle is a step-by-step process involved in the development of a software product. The whole process is generally classified into a set of steps and a specific operation will be carried out in each of the steps

Front 10

WATERFALL MODEL PHASE OR MILESTONE

Back 10

-REQUREMENTS
-Planning
-Analysis
-Design
-Development OR CODING
-Testing
-UAT
-Deployment
-Maintanence

Front 11

WATER FALL

Back 11

Popular process module for developing and designing software programs to meet specific customer needs.

Front 12

V SHAPE MODEL

Back 12

The V model gets its name from the fact that the graphical representation.The basic steps involved in this methodology are more or less the same as those in the waterfall model. However, this model follows both a 'top-down' (VERIFICATION) as well as a 'bottom-up'(VALIDATION) approach.The benefit of this methodology is that in this case, both the development and testing activities go hand-in-hand.

Front 13

VERIFICATION

Back 13

TYPICALLY INVOLVE REVIEW AND MEETING TO EVALUATE DOC, PLAN, REQUIREMENTS IS GOING TO BE DONE BY INSPECTION MEETING,WALK-THROUGH, CHECKLIST. Quality control process to check whether or not a product complies with regulations, specifications. BUILD GOOD PRODUCT.

Front 14

VALIDATION

Back 14

ACTUAL TESTING AND TAKE PLACE AFTER VERIFICATION. "The QUALITY process of evaluating a system during or at the end of the development process to determine whether it satisfies specified user requirements.

Front 15

QUALITY CONTROL

Back 15

The process by which product quality is compared with applicable standards, and the action is taken when non conformance is detected.

Front 16

ADHOC

Back 16

Adhoc testing is a commonly used term for software testing performed without planning and documentation.The tests are intended to be run only once, unless a defect is discovered.

Front 17

STATIC TESTING

Back 17

It is primarily syntax checking of the code and/or manually reviewing the code or document to find errors. This type of testing can be used by the developer who wrote the code, in isolation. Code reviews, inspections and walkthroughs are also used.

Front 18

DYNAMIC TESTING

Back 18

Dynamic testing is nothing but functional testing. It is used to test software by executing it.

Front 19

Agile Process:

Back 19

Agile aims to reduce risk by breaking projects into small PIECE, time-limited modules with each iteration being approached like a small, self-contained mini-project, each lasting only a few weeks. Each iteration has it own self-contained stages of analysis, design, production, testing and documentation. In theory, a new software release could be done at the end of each iteration, but in practice the progress made in one iteration may not be worth a release and it will be carried over and incorporated into the next iteration. The project's priorities, direction and progress are re-evaluated at the end of each iteration.

Front 20

BUG

Back 20

Product is still not yet released in the market. Found before production.

Front 21

DEFECT

Back 21

Product is released in the market. Found after production.

Front 22

SEVERITY

Back 22

is from the technical side.
Unacceptable Risk - if the Product /application Crashes, Incorrect parameter value (ex. Instead of 60 Heart Rate 80 Heart Rate is displayed)
Design NC - Patient information not displayed under User Information.
Minor Issue - IP address textbox should be grayed out when DHCP is selected
Improvement Opportunity - Some cosmetic Documentation Issue

Front 23

PRIORITY

Back 23

Priority refers to the "Urgency" with which the incident has to be fixed. This is set by the lead.
In most of the cases a critical incident can be of high priority.
IT IS FROM THE BUSINESS SIDE AND RESPOND FOR FINANCE.

Front 24

What to do when a defect is not reproducible:

Back 24

1. Test on another setup.
2. Take pictures and video the first time the defect occurs.
3. Save and Attach the Log file.

Front 25

QUALITY CENTER OR TEST MANAGEMENT TOOLS

Back 25

TO HELP TESTER TEAM ORGANIZE OR EXECUTE THE REQUIREMENTS, TEST PLAN, TEST CASE, AND SING TO DEFECT

Front 26

Testing Review - Dos and Dont's FOR Author

Back 26

Be open to feedback.
Observe the review process.
Remember that there is no product that is defect-free.

Front 27

Testing Review - Dos and Dont's FOR Reviewer

Back 27

Review the Product not the Producer.
Do not accuse.
Avoid discussions of styles - stick to technical correctness.

Front 28

Testing IPO (Inputs, Process and Outputs)

Back 28

inputs:
Plan - Schedule
Data -To be transacted, PROTECTED
Environment - Hardware,Web Servers, Browers.
Test Cases - TEST CASE ID, Description, Expected actual result, status, data.

Front 29

Testing IPO (Inputs, Process and Outputs)

Back 29

- Verify if the test cases are reviewed and approved.
- Verify that you are working in the test environment (Not Development Environment).
- Execute the Work Product.
- Apply test scenarios.
- Observe actual results and behavior.
- Record the actual results and observations.

Front 30

Testing IPO (Inputs, Process and Outputs)

Back 30

Test Results - Actual results, Expected results.
Defects Log - Priority, Severity, Summary, for whom, Date detected.
Test Report - Summary of testing done,