bvt

Within the range of tests that consistently pass, which ones should be in the BVT?

Service-Oriented Architecture (SOA) projects typically rely on the automated source code build, deploy, and build-verify-test (BVT) cycle.

To integrate with it, you can install the Build Forge agent into your build server, which is running the Build-Deploy-BVT script.

While every book on testing says to test the boundary conditions, the BVTs may not be the place to do that.

BVT test failures should be something you're willing to act on immediately.

For example, you could apply the BVT tag to a pool of agents that are designed to run your BVT tests.

This program invokes all Build-Deploy-BVT steps irrespective of build platforms.

In other words, the failures must be important.

Then select the test metadata file that contains the BVT test list you created in.

As part of globalization, the BVT will be executed in supported locales of the software product that is available.

Now you can perform the BVT with the unit test framework.

As part of the GVT, BVT and FVT execute in all supported locales.

Add your solution and the BVT to source code control.

The BVT also has its fair share of detractors.

Tests outside most user scenarios shouldn't be in the BVTs.

Create a Build Type, specifying to run the BVT test list as part of the build

To create the BVT build type