How to differentiate between rat, fast, Toft, and FET in Test Cases

Original article: http://blog.codylab.com/testcase-categorization/

I believe that understanding the classification of test cases can accelerate the design and development of test cases and give developers a better understanding of the test objectives. Generally, test cases can be divided into at least the following types:

• Release Acceptance Test (rat)
• Functional acceptance simple test (FAST)
• Task-oriented function test (Toft)
• Force-Error Test (FET)
• Boundary Test
• Volume Test
• Stress Test

When I was learning to write test cases, I asked my predecessors for different types of test cases. People cannot tell the simplest possible reasons are different rat and fast. Acceptance Test of rat and fast. Its literal meaning is not easy to see. In fact, for me, the test is divided into two categories, one is normal software under testing measurement, or testing error handling Fet. It can be divided into rat, fast, Toft, boundary, volume, and stress. However, because it constitutes a software. Under normal circumstances, if a test is required, passing the test only indicates a certain degree of protection of its quality. However, in the first test, what is the post test? Of course, this is the first important test. The importance of rough points can be roughly divided into: Rat
> Fast> Toft = boundary = FET> volume = stress
Rat is used to determine whether the test can be generated in some processes. If the test case of rat fails, the QA personnel can request untested construction and establish the test before continuing the test. The next test cannot be executed because of a major defect in this build. Therefore, the number of rat test cases should be very small in theory. For example, a part of the installation must have at least one mouse. After all, if the software cannot be installed together, is there a way to test it.

The fast module can be regarded as the most important testcase. If it is not passed, it may affect the future of tov. There is no way to continue testing. It can be selected from several test cases in the most important modules.

Toft, basically as long as you don't take it as rat and fast are testing the remaining test cases.

Fet is intended to make some program errors, regardless of the error handle to properly handle test cases can usually find a lot of defects, because, after all, developers will be relatively easy to ignore some of the error handle

The boundary test specifically measures some critical situations, such as the highest and lowest values of the variable, and then the opposite. Some margin measurement error handles. Capacity testing and stress testing are not functional testing.