Microsoft Solution Architecture (Module 7) (2)

zhaozj2021-02-17  50

3) Test Solution

I. Test

All mistakes must be resolved

Verify the elements of the verification scheme for specifications

Exposure design error

Exposure from unbained user operations

Test all scheme elements

Test: Quality of Access Projects

Test is part of the generated, not a separate activity

Ii. Test type

All tests will expose the wrong plan

Test type coverage program features a wide range

Test should be based on the feature to verify

III. Overlay test

Overlay test

l Attempt to test the fully test scheme

l Test the code library for fully testing solutions

l is mainly used in the development phase

Covered the type of test

l unit

l function

l check in

l Build a verification

l regression test

IV. Execution Test

Use tests:

l Trial to successfully complete the use of plots

l Test the product in the expected environment

l is mainly used for stable stages

Type of test

l configuration test

l-compatible test

l pressure test

l Performance test

l Document and help file test

l Availability test

V. Error nature

Not all bugs are erroneous, but all errors are bugs

All BUGs are reviewed and resolved before publishing.

BUG: All issues triggered during the use of the program

Vi. Effective Management Error

Track the results to recognize the test value

Programming your error tracking process

Efforts to classify and classify

Promote the decision with error analysis

VII. Tracking error

Report -> Row Priority and Assignment -> Solving -> Close

VIII. Error classification

Category BUG makes them can be used

Categories:

l severely

l priority

By providing BUG classification re-estimation of quality standards

IX. Correcting Error

Correct the error by expressing them in a consistency

How to correct the error by specifying the error label

Correcting errors is closing the intermediate steps before they

2) Module summary

The goal of the development phase is to create a variety of features and items that can be submitted.

The internal release cycle of daily build-forms helps break down complex project into manageable tasks

The goal of the test is the quality of the access scheme

Different types of tests are used to express the extensive characteristics of the program

All errors must be reviewed and resolved before publishing

转载请注明原文地址:https://www.9cbs.com/read-28665.html

New Post(0)