Test fixture

A test fixture is something used to consistently test some item, device, or piece of software. Test fixtures can be found when testing electronics, software and physical devices.

## Contents

* 1 Electronics
* 2 Software
* 2.1 Setup
* 2.2 Advantages and disadvantages
* 2.3 Practices to avoid
* 2.4 Examples
* 3 Physical testing
* 4 See also
* 5 References
* 6 External links

## Electronics

In testing electronic equipment such as circuit boards, electronic components, and chips, a test fixture is a device or setup designed to hold the device under test in place and allow it to be tested by being subjected to controlled electronic test signals.

Side connectors, centering pins, test needles, pre-centering parts. A Functional Test Fixture is a complex device to interface the device under test (DUT) to the automatic test equipment (ATE)

Examples are a bed of nails tester or SmartFixture.

## Software

A software test fixture sets up a system for the software testing process by initializing it, thereby satisfying any preconditions the system may have.[1] For example, the Ruby on Rails web framework uses YAML to initialize a database with known parameters before running a test.[2] This allows for tests to be repeatable, which is one of the key features of an effective test framework.[1]

### Setup

Test fixtures can be set up three different ways: in-line, delegate, and implicit.

1. In-line setup creates the test fixture in the same method as the rest of the test. While in-line setup is the simplest test fixture to create, it leads to duplication when multiple tests require the same initial data.
2. Delegate setup places the test fixture in a separate standalone helper method that is accessed by multiple test methods.
3. Implicit setup places the test fixture in a setup method which is used to set up multiple test methods. This differs from delegate setup in that the overall setup of multiple tests is in a single setup method where the test fixture gets created rather than each test method having its own setup procedures and linking to an external test fixture.[3]

### Advantages and disadvantages

The advantage of a test fixture is that it allows for tests to be repeatable since one is always starting with the same setup every time. Test fixtures also ease test code design by allowing the developer to separate methods into different functions and reuse each function for other tests. It also preconfigures tests into a known state at start instead of working with whatever was left from a previous test run. A disadvantage is that it could lead to duplication of test fixtures if using in-line setup.[1][3]

### Practices to avoid

It is considered bad practice when implicit test fixtures are too general, or when a test method sets up a test fixture and does not use it during the test. A more subtle issue is if the test methods ignore certain fields within the test fixture. Another bad practice would be a test setup that contains more steps than are needed for the test; this is a problem seen in in-line setup.[3]

A test case is considered "unsafe" when it modifies its fixture(s). An unsafe test case can render subsequent tests useless by leaving the fixture in an unexpected state. It also causes the order of tests to be important: a modified fixture must be reset if more tests are to be run after an unsafe test.[1]

### Examples

Examples of fixtures include loading a database with a specific known set of data, erasing a hard disk and installing a known clean operating system installation, copying a specific known set of files or the preparation of input data and set-up/creation of mock objects.

Software which is used to run reproducible tests systematically on a piece of software under test is known as a test harness; part of its job is to set up suitable test fixtures.

In generic xUnit, a test fixture is all the things that must be in place in order to run a test and expect a particular outcome.[4]

Frequently fixtures are created by handling setUp() and tearDown() events of the unit testing framework. In setUp() one would create the expected state for the test and in tearDown() it would clean up what had been set up.

Four phases of a test:

1. Set-up
2. Exercise, interacting with the system under test
3. Verify, determining whether the expected outcome has been obtained
4. Tear down, to return to the original state

## Physical testing

In physical testing, a fixture is a device or apparatus to hold or support the test specimen during the test. The influence of test fixtures on test results is important and is an ongoing subject of research.[5]

Many test methods detail the requirements of test fixtures in the text of the document.[6][7]

* Test fixture on universal testing machine for three-point flex test

* Hydraulic system testing on fixture

* jet engine fixtures for operational testing

Some fixtures employ clamps, wedge grips and pincer grips.

* pincer clamps max. 50 kN spring-biased

* offset compensated wedge grip max.50 kN

* different vice and screw grips of a German manufacturer

Further types of construction include eccentric roller fixtures, thread grips and button head grips and rope grips.

* symmetric roller grip, self-closing and self-adjusting

* multiple button head grip for speedy tests on series

* small rope grip 200N to test fine wires

* very compact wedge grip for temperature chambers providing extreme temperatures

Mechanical holding apparatuses provide the clamping force via arms, wedges or eccentric wheel to the jaws. Additionally there are pneumatic and hydraulic fixtures for tensile testing that allow very fast clamping procedures and very high clamping forces.

* pneumatic grip, symmetrical, clamping force 2.4 kN

* heavy duty hydraulic clamps, clamping force 700 kN

* Bending device for tensile testing machines

* Equipment to test peeling forces up to 10 kN

## See also

* Unit testing

## References

1. ↑ 1.0 1.1 1.2 1.3 Pereira da Silva, Lucas (June 10, 2016). "Execution and code reuse between test classes". 2016 IEEE 14th International Conference on Software Engineering Research, Management and Applications (SERA). pp. 99–106. doi:10.1109/SERA.2016.7516134. ISBN 978-1-5090-0809-4. https://www.computer.org/csdl/proceedings/sera/2016/0809/00/07516134-abs.html.
2. ↑ "A Guide to Testing Rails Applications". http://guides.rubyonrails.org/testing.html.
3. ↑ 3.0 3.1 3.2 Greiler, Michaela; Zaidman, Andy; van Deursen, Arie; Storey, Margaret-Anne (2013). "Strategies for Avoiding Text Fixture Smells during Software Evolution". 10th IEEE Working Conference on Mining Software Repositories (MSR). doi:10.1109/MSR.2013.6624053. http://www.michaelagreiler.com/blog/wp-content/uploads/2013/05/MSR_2013_camera-ready.pdf. Retrieved 24 January 2014.
4. ↑ Meszaros, Gerard (2007). xUnit Test Patterns: Refactoring Test Code. Addison-Wesley Professional. ISBN 978-0-13-149505-0. http://buhoz.net/public/books/computacion/desarrollo/metodologias/agiles/xUnit.Test.Patterns.Refactoring.Test.Code.2007.pdf.
5. ↑ Abadalah, MG; Gascoigne, HE (1989). The Influence of Test Fixture Design on the Shear Test for Fiber Composite Materials. ASTM STP.
6. ↑ ASTM B829 Test for Determining the Formability of copper Strip
7. ↑ ASTM D6641 Compressive Properties of Polymer Matrix Using a Combined Loading Compression Test Fixture

## External links

* Unit Testing with JUnit, by Yoonsik Cheon
* The Low-Down on fixtures, from A Guide to Testing Rails Applications

0.00

(0 votes)

|

Retrieved from "https://handwiki.org/wiki/index.php?title=Software:Test_fixture&oldid=3897256"