Is Build Verification Test carried out at the level of unit tests?

Question

Software testing

If not, please provide an example. From the definition, it is not entirely clear how it is generally checked before it gets into testing. If this is not about unit tests, then the difference from smoke testing or consistency testing is not clear.

Build Testing or Build Verification Test - testing aimed at determining whether the released version complies with the quality criteria for starting testing. According to its goals, it is an analogue of Smoke Testing, aimed at accepting a new version for further testing or operation. It can penetrate further into the depths, depending on the quality requirements of the released version.

Answer 1

I propose to start with definitions. BVT can be considered a conditional analogue of Smoke testing. Initially, Smoke testing was performed before deeper testing and consisted of a small number of the most critical tests. Smoke testing answers the question "does the product meet the minimum test readiness criteria".
BVT is most often a set of automated tests that are run as part of the CI/CD Pipeline and answer the question "does the product meet the necessary and sufficient requirements to pass the build phase". Those. One of the key differences between BVT and Smoke is that BVT stands for automated tests.
Next, to your question. The term unit testing is very controversial. If you ask 3 experts about what is a unit test, you will get at least five different opinions. From the point of view of BVT, it does not matter at all what kind of tests these are, unit/integration/e2e. The speed of their implementation is important (a very common goal is up to 10 minutes). In most cases, the BVT will consist of either system-level tests or tests at various levels.

Answer 2

1. Static code analysis
2. Unit testing
3. Deploy to the bench, if necessary
4. Smoke Integration testing, if necessary
5. Sanity System testing, if necessary