Unit 8 Flashcards

1
Q

What is UAT

A

User acceptance testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

is a type of testing performed by the end user or the client to verify/accept the software system before moving the software application to the production environment.

A

User acceptance testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What is the main purpose of UAT

A

is to validate end to end business flow.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

is carried out in a separate testing environment with production-like data setup.

A

User acceptance testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

UAT is performed by

A

Clients,
End-users

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Prerequisites of User Acceptance Testing:

A
  • Business Requirements must be available.
  • Application Code should be fully developed
  • Unit Testing, Integration Testing & System
    Testing should be completed.
  • No Showstoppers, High, Medium defects in
    System Integration Test Phase
  • Only Cosmetic error is acceptable before UAT
  • Regression Testing should be completed with no
    major defects
  • All the reported defects should be fixed and
    tested before UAT
  • Traceability matrix for all testing should be
    completed
  • UAT Environment/Staging Environment must be
    ready
  • Sign off mail or communication from System
    Testing Team that the system is ready for UAT
    execution
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

How to execute UAT Tests

A
  • Analysis of Business Requirements
  • Creation of UAT test plan
  • Identify Test Scenarios
  • Create UAT Test Cases
  • Preparation of Test Data (Production like Data)
  • Run the Test cases Record the Results
  • Confirm business objectives
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

ANALYSIS of BUSINESS REQUIREMENTs

A

*Project Charter
*Business Use Cases
*Process Flow Diagrams
*Business Requirements Document(BRD)
*System Requirements Specification(SRS)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

outlines the strategy that will be used to verify and ensure an application meets its business requirements.

A

Creation of UAT PLAN

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Creation of UAT PLAN documents what?

A

entry and exit criteria for UAT,
Test scenarios,
Test cases approach and timelines of testing.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Identify the ______ with respect to high-level business process and create test cases with clear test steps.

A

Test scenarios

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

it should sufficiently cover most of the UAT scenarios.

A

Test cases

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

are input for creating the test cases.

A

Business Use cases

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

It is best advised to use live data for UAT. Data should be
scrambled for ______ and _______ reasons. Tester should be
familiar with the database flow.

A

Privacy and Security

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Execute test cases and report bugs if any. Re-test bugs once fixed. Test Management tools can be used for execution.

A

Run and Record the results

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Business Analysts or UAT Testers needs to send a sign off
mail after the UAT testing. After sign-off, the product is good to go for production.
Deliverables for UAT testing are:

A
  • Test Plan
  • UAT Scenarios
  • Test Cases
  • Test Results
  • Defect Log
18
Q

These are the qualities of UAT Testers

A

should possess good knowledge of the business,
independent, think as an unknown user to the system, should be Analytical and Lateral thinker

19
Q

These are people who understand the business requirements or flows can prepare test and data which are realistic to the business.

A

Tester, Business Analyst, Subject Matter Experts

20
Q

Prioritization in project management

A

Low priority (light green)
Medium priority (orange)
High priority (purple)
Critical (red)

21
Q

TASK Priority CATEGORIES

A

New Feature (dark green)
Enhancement (blue)
Hotfix (light red)

22
Q

types of Project Health

A

On Track, At Risk, Off Track

23
Q

types of Project Status

A

Active, Completed, Cancelled, On Hold

24
Q

Risk/Issue Details

A

Issue, Risk

25
The project is on schedule, within scope, and within budget. Project resources are available for project activities when needed.
On Track
26
There are risks and/or issues that might impact achievement of the project's objectives.
At Risk
27
There are significant issues that have impacted achievement of the project's objectives.
Off Track
28
The project is currently being worked on by the project team.
Active
29
Work on the project has finished, and all deliverables/tasks have been completed.
Completed
30
The project has not finished, and work on the project will not continue.
Cancelled
31
The project has not finished, and work on the project has been temporarily suspended.
On Hold
32
An event that has happened and may impact achievement of the project's objectives if not resolved
Issue
33
A potential event that may impact achievement of the project's objectives if it does happen.
Risk