Smoke test and random test

Smoke test and random test
From 51testing

There are many types of software testing. Each test has its own purpose and implementation means. This article describes two less common test types: Smoke test and random test.

Smoke test

Smoke testing is said to be the name of Microsoft. In Chapter 14th of Microsoft Project survival rules, "Building Process", the current smoke test project is executed by developers on the software of the personal version, identify that the new program code does not fail.

The name of the smoke test can be understood as it takes a short time, and only one bag of smoke is enough. Some people think that it is an image similar to the basic function inspection of the new circuit board. After soldering any new circuit board, the system first Performs electrical check. If a design defect exists, the circuit board may be short-circuited, and the Board smoke.

The smoke test object is the version of each newly compiled software that needs to be officially tested. The purpose is to confirm that the basic functions of the software are normal and subsequent formal tests can be conducted. The implementer of the smoke test is the version compiler.

In general software companies, during software compilation, multiple internal versions (Builds) need to be compiled, but only a limited number of versions need to be officially tested (according to the project development plan ), these intermediate test versions to be executed. After compilation, the software compiler needs to perform basic performance validation tests, such as whether the software can be correctly installed/uninstalled and whether the main functions are implemented, whether there are bugs such as serious crashes or serious data loss. If you pass this test, you can perform the formal test according to the formal test documentation. Otherwise, you need to re-compile the version and execute the version again to receive the validation test until it is successful.

Some companies use Build Sanity Check to test the basic functions of the new version ). For the new version of the compiled localization software, in addition to the various test checks mentioned above, you also need to check whether all the files that should be localized are correctly included in the new localization version. By using a file and directory structure comparison tool, you can first compare the number of files in the files and directories of the source and local versions, such as the file name and file date, this process is called Build Image Check ). Second, install the source and local versions respectively, and compare the number of files, file names, and file dates in the installed files and directory structures, this process is called Build Installing Check ).

Random test

In addition to testing according to the test samples and instructions, random testing (Ad-hoc testing) is also required in software testing ), the function and performance of the software are checked based on the tester's experience. Random testing is an important supplementary means to execute the sample test according to the test manual. It is an effective way and process to ensure the test coverage integrity.

The random test mainly involves a retest of some important functions of the software under test, and also includes the tests that are not covered by the current test example (TestCase. In addition, software updates and new functions should be tested. Focuses on some special points, special use environments, concurrency, and inspection. In particular, re-testing of major bugs found in previous tests can be performed in conjunction with Regressive testing.

In theory, random testing is required for each software version to be tested, especially for the final version to be released. Random testing is best performed by testers who are familiar with the software under test with rich testing experience. The more familiar the software to be tested, the easier it is to perform random tests. Only by accumulating test experience, including test execution and Analysis of defect tracking records, can we continue to summarize the results.