acceptance test造句

Specification for acceptance test of water-cooling tower

This paper presents the turbine model acceptance test and the test results of Feilaixia hydropower station.

For example, you can do it after functional test, or you can do it after UAT (user acceptance test).

Test case generation for acceptance tests differs from other test phases due to some distinct deviations between the underlying premise of this test level and the others.

Then go nuts: smoke tests, any acceptance test suite you have, and of course regression and exploratory testing.

Alternately, you may empirically reflect on the additional time needed to thoroughly capture and review requirements, project plans, acceptance test criteria, and other required artifacts.

As I mentioned in the test-first development practice section of last month's installment, acceptance testing is the customer half of the XP testing picture.

How could testers remain involved in the requirements elicitation activity while immersed in system, integration, and user acceptance test, all at the same time?

We thought our intention to use the test scripts had been made clear in the acceptance test plan, but we now realized our wording in that plan was ambiguous.

This testing was important not only in preparation for the customer acceptance tests, but also because it exercised the system heavily and provided insight into flaws in the test scripts.

The point is that acceptance tests help customers gauge how "done" the project is.

RUP acknowledges four levels of testing: unit testing, integration testing, system testing, and acceptance testing.

Not all of the acceptance tests have to pass all the time.

Submit benchmark and coordinate control point to Party B in written form and make an acceptance testing on site;

For acceptance testing, when properly implemented, use cases shorten the gap between the tester's conceptualization and the reality of user goals.

I wanted to reduce the task of collecting use cases and turning them into client acceptance tests, which were then reused as a training resource for new developers.

For each named feature, there are one or more automated acceptance tests which, when they work, will show that the feature in question is implemented.

Just above this level are some larger level practices such as system metaphor; continuous integration; on-site customer; collective ownership; acceptance testing; planning game; and short releases.