Acceptance Testing or Acceptance Testing

Lecture

A formal testing process that verifies that the system meets the requirements and is conducted with the goal of:

determining whether the system meets the acceptance criteria;
the decision of the customer or other authorized person is an application or not.

Acceptance testing is performed based on a set of typical test cases and scenarios developed based on the requirements for this application.
The decision to conduct acceptance testing is made when:

the product has reached the required level of quality;
the customer is familiar with the Acceptance Work Plan ( Product Acceptance Plan ) or other document that describes a set of actions related to the acceptance testing, the date of the performance, those responsible, etc.

The phase of acceptance testing lasts as long as the customer does not make a decision about sending the application for revision or issuing the application.

The RUP acceptance test plan template can be downloaded by clicking on the link: RUP Product Acceptance Plan

Comments

To leave a comment

If you have any suggestion, idea, thanks or comment, feel free to write. We really value feedback and are glad to hear your opinion.

To reply

Comment

To confirm that you are not a bot, answer:

Name

Email(not published)

Vote

Lectures and tutorial on "Quality Assurance"

Terms: Quality Assurance

Tester (QA)

QA specialty. Introduction to testing. Basic definitions

Software development process (waterfall, iterative and spiral development model), development methodology

Types and types of testing. Testing levels

Requirements. Requirement Analysis, Requirement Types , SWEBOK

Basic QA (Test) artifacts

Ошибки (Bugs), Баг Репорт (Bug Report) системы отслеживания ошибок

Web testing

Mobile testing

Team and Roles

Jira - the basics

Work with the client, Ethics of communication with the client by mail, through messengers and by telephone, types of clients and interactions take off

Functional Testing or Functional Testing

Security Testing or Security and Access Control Testing

Interoperability Testing or Interoperability Testing

Load testing or performance testing

Smoke Testing or Smoke Testing

Build Testing or Build Verification Test

Sanitary Testing or Consistency / Health Testing or Sanity Testing

Regression Testing or Regression Testing

Testing Installation or Installation Testing

Usability Testing or Usability Testing

Failover and Recovery Testing

Configuration Testing or Configuration Testing

Alpha testing and Beta testing of software products

Component or Unit Testing

Integration Testing

System Testing (System Testing)

Acceptance Testing or Acceptance Testing

Testing process

Conditions for testing

Test Design Test Coverage Techniques of Design Test

Quality assurance - basic concepts and definitions

Software quality

How to start quality assurance?

Creating and Using Templates

Creating instructions or sequencing

Using Standards and Processes

Analysis of past projects

Use of Defect Data

Use the knowledge gained

Quality Assurance Recommendations

Quality Assurance Metrics

QA Interview

Quality Assurance Concept

Changing processes and procedures

Automated Software Testing - Basic Concepts

Load Testing - Automation

Automated Functional Testing

Usability consulting

Expert Usability Assessment Report

Testing object-oriented software systems

Types of errors and basic debugging principles.

Principles of testing

Mock-object and dummy- (stub function) use in testing

Load testing a web server using ab Apache HTTP server benchmarking tool

Coverage of graphs in software testing

Testing based on entity state diagrams

10 defects, errors and risks in the software life cycle

11 SPECIFICATIONS OF QUALITY OF SOFTWARE TOOLS

12 SELECTION OF QUALITY CHARACTERISTICS IN PROJECT PROGRAMS

13 VERIFICATION, TESTING AND EVALUATING THE CORRECTNESS OF SOFTWARE COMPONENTS

14 INTEGRATION, QUALIFICATION TESTING AND TESTING OF PROGRAM COMPLEXES

15 SUPPORT AND MONITORING OF SOFTWARE FACILITIES

Statistical model of Mills - evaluation of the number of errors in the program code,

13.2. Processes and tools for testing software components

11.3. Constructive characteristics of the quality of complex software

Auto-Auto-test, (AA-auto-test): double automation in software testing