| ylbtech- test - test mode: Smoke Tests |
The term source from the hardware industry . After a hardware or hardware components change or repair directly to the device is powered . If you do not smoke, the assembly passed the test . In software, the "smoke test" is the term used to describe the process of verifying prior to changing the code embedded in the source tree of the product of these changes . After reviewing the code, smoke testing is to identify and fix software defects are the most cost-effective way. Smoke test designed to confirm the code change will run as expected , and will not destroy the entire version of stability .
| 1. Back to top |
1、
- Chinese name: smoke test
- English name: smoke testing
- The membership: free tests
- Industry: Computer
table of Contents
2、
| 2. Return to top |
1、
Outline
Smoke testing is a software development process for the software version of the package
validation policy Quick basic functions
, it is a means of verification to confirm the basic functions of the software, not in-depth testing of the software package version. Smoke testing is also pre-tested prior to detailed tests on the software version of the package, perform a smoke test of the
main purpose is to quickly verify the basic functions of the software is defective
. If the smoke test case test is not passed, you do not need to do further testing. Example set determined by testing prior to smoke smoke tests, the basic function of software in Example claims cover set. This method of verification threshold version of the package after the package is usually referred to as software package version verification cases.
Smoke testing belonging
HLT (highleveltest) test
,
the HLT
generally refers to
the SDV (System Design Verification) / SIT (System Integration Testing) / SVT (System Verification Test)
and other test activities. HLT is standing on the perspective of the whole system version for testing, the test object is a complete product rather than the product inside the module, including a common HLT test
system testing and acceptance testing
.
Smoke testing can be performed manually, can be automated execution.
Stable system for automated smoke test, system integration process suitable for manual testing smoke
, because smoke test automation scripts in dynamic content changes, changes in the maintenance workload is relatively large.
Smoke testing (smoke testing), Microsoft is said to be from the name. In the "Microsoft Project Survival Rule" a book Chapter 14, "Building Process" on smoke testing, smoke testing project developer is performed on a personal version of the software, identify new program code not at fault. Name smoke tests can be understood as the kind of short test time-consuming, with only a bag of tobacco effort is enough. Some people think that analogy is the image of the new
board
basic function tests. Any new board after a good weld, the first power check, if the design defects, the circuit board may be short-circuited, the board smoke.
classification
The object is a smoke test version of the software needs of each new compilation of official tests. By smoke test before the software code to compile and deliver a formal test,
first try to eliminate the error surface, reduce the burden of post-test
. Performer smoke test is the version of the compiler personnel. Therefore we can say, smoke testing is a pre-test. In the actual software testing, the smoke test is different at different stages of software development. They can be roughly divided into three categories:
1) forming an integrated version of the previous test: Verify the successful implementation of the respective units, and to ensure smooth integration test version;
2) forming an integrated test version: to ensure that the new or changed without destroying the integrated version of code is completed and stability;
3) pre-test post-correction of defects: Defect correction made for each defect must first conduct smoke tests in a clean environment links, to update the software version of the test.
application
Smoke test object is compiled each new version of the software requires formal testing, the purpose is to identify
the software
basic function properly, can make subsequent formal testing. Performer smoke test is the version of the compiler personnel.
In general software companies, software in the preparation process, the internal need to compile multiple versions (Builds), but only a limited number of versions need to perform a formal test (according to the project development plan), these intermediate test version to be performed in just compiled out, software compilers need for basic performance
validation tests
, such as whether you can install the correct /
uninstall
, the main function is realized, the existence of a serious crash or data loss and other serious Bug. If it passes the test, it can be formally tested according to the official test documentation. Otherwise, you need to be recompiled version, re-executed version can receive confirmation test until successful.
status quo
The basic features of the new version of the confirmation test, some companies called
version health check (Build Sanity the Check)
.
The new version of the compiler software localization, in addition to various checks mentioned above, but also check whether the new localized version includes all the correct file should be localized. Files may be employed and
directory structure
comparison tool, first version number of the file and comparing the source language localized versions of files and directories, file name and file date, this process is called
version mirror checking (the Build the Check Image)
; second, respectively, installation source language version and a localized version number of file and directory structure of the comparison installation, file name and file date, this process is called
version installed check (Build installing the check)
.
significance
Smoke test, a lower share of some proportion of time in the software life cycle, but also has focused on the characteristics of the light through the details, it is often developers, testers ignored. In fact, smoke testing software testing process is an integral node, a good smoke testing process is of great significance for enhancing the efficiency of software testing.
(1) smoke test
is a test of overall software quality
.
By smoke test can quickly confirm whether the software can test the access conditions to avoid fully operational after the formal testing phase even in the post-test was found obstructive defects seriously affect the progress of the test cases waste of resources.
(2) smoke test is the
test personnel familiar with the testing process
.
By smoke test, testers can quickly become familiar with the overall test process, this aspect helps testers to develop accurate test schedule, reasonable arrangements for the progress of work; it also helps testers do related equipment, data preparation in advance lay the foundation for the official launch of the test.
Precautions
Smoke test execution, and the difference between formal testing is that the two different emphases, smoke testing
is concerned obstructive defects
, including
but not limited to, the process fails, the main function is not implemented and so on
, and formal testing is
part of a comprehensive and detailed test
a need to find all possible defects to distinguish according to its severity. Smoke testing process, should be noted that:
1, developed cooperative
Smoke testing phase has several characteristics, namely, that there may be more phases of software defects, especially
obstructive defects
, testing at any time may come to a standstill; the second is the phase flow testers of the software, the more functions familiarity low, there will inevitably be the appropriate test methods can not find even can not find the function module appears to delay the progress of the test; the third is the phase of time is generally only the entire software life cycle of a very small portion, which requires developers real-time In response, solve various problems as soon as possible. Therefore, in the smoke testing phase, work is very important testers and developers.
2,
focus on efficiency
Smoke test
should be based on efficiency first, try to shorten the test time and improve test efficiency
. The main concern should be the premise processes, focusing on function, grasping the key defect inspection data preparation, such as a page for unsightly defects such as poor user experience may be selective filter stage in smoke. For example: test system logon, the focus should be for the user name and password, enter verification code and submit complete, check for illegal characters, login box is beautiful, the error message is accurate all belong to a secondary concern, not included smoke testing range.
3, cases assessed by
A process of smoke testing process but also for the assessment of test cases, to take full advantage of this phase, the early form of test cases to test in a timely manner to supplement cases, deletions and amendments, making the actual case more fit, more enforceable.
2、
| 3. Back to top |
·
·
| 4. Top |
| 5. Top |
1、
2、
| 6. Back to top |
 |
Author: ylbtech Source: http://ylbtech.cnblogs.com/ This article belongs to the author and blog Park total, welcome to reprint, but without the author's consent declared by this section must be retained, and given the original connection in the apparent position of the article page, otherwise reserves the right to pursue legal responsibilities. |