Testability tactics

It refers to the test software by testing the easiness (typically based on a test run) discloses software defects. In the development of a well-designed system cost, mostly used in the test. If the software designer can reduce this cost, it will receive a huge return. To properly test the system, we must be able to "control" input and internal state of each component, and "observation" output. This is usually done by using the "Test Tools", which is a specially designed software, software for performing the tests. This may as data on a variety of interfaces playback recorded as simple as it may be as complex as the engine combustion chamber test.

Testability tactics

Be objective test of tactics is to allow the completion of an incremental software development, more easily test the software.
Next, the test for tactical discussion categories: providing an input and capture the output; internal monitor.

input Output

There are three kinds of tactics for input and output management tested.

• Recording / playback
  recording / playback means to capture information across the interface, and a dedicated test software as its input. Across an interface in normal operation information is stored in a repository, which represents the output from one component input and passed to a component. This makes it possible to record information input to generate the test in which one component of the output of the comparator and the test stored for later.

• The interface and implementation separation of
  the interface instead allows to achieve the separation, to support various testing purposes. Point in the absence of implementation allows the assembly is occupying, the remainder of the system tested. Instead of a special assembly for a component assembly can be made to act as a test tool is replaced by a remaining portion of the system.

• Specialized access route / Interface
  test interface with specialized tools and allows testing independent of its normal operation, or to capture the specified variable value component. For example, metadata may be provided by specialized interface, the interface testing tool with which to promote their activities. It should be specialized interfaces and access routes and access routes and interfaces required for the function separated. The test interface layered architecture means that the test can be applied at any level architecture, and already has a test function to observe the response.

Internal monitoring

Built-in monitor
assembly state can be maintained, load performance, capacity, security or other information may be accessible through the interface. This interface may be a permanent interface to the assembly, or may be introduced by temporary instrumentation interface techniques, such as pretreatment or aspect-oriented programming macros. A common technique is to record the event when the monitor status is activated. Monitoring the state actually increased testing, because as the close monitoring may be necessary to repeat the test. Despite the additional testing will take some overhead, but visibility while filling assembly activity is increased, this is worth it.

Link: https: //www.jianshu.com/p/344c69a14d71