0% found this document useful (0 votes)
33 views2 pages

1 What Is A Fast Test

A Fast-test is a test philosophy that aims to achieve high testing value with minimal effort. It advocates testing from the user perspective without depending on the UI framework. Fast-tests isolate code dependencies and cloak I/O to make them always runnable and idempotent. By following simple rules, Fast-tests can test 80-90% of an application's presentation and business logic without the brittleness of end-to-end tests. The document promotes building robust Fast-test suites first before adding integration and end-to-end tests judiciously where needed. The overall goal is for engineering teams to have confidence to deploy software without relying on others to validate it.

Uploaded by

Nitish
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
33 views2 pages

1 What Is A Fast Test

A Fast-test is a test philosophy that aims to achieve high testing value with minimal effort. It advocates testing from the user perspective without depending on the UI framework. Fast-tests isolate code dependencies and cloak I/O to make them always runnable and idempotent. By following simple rules, Fast-tests can test 80-90% of an application's presentation and business logic without the brittleness of end-to-end tests. The document promotes building robust Fast-test suites first before adding integration and end-to-end tests judiciously where needed. The overall goal is for engineering teams to have confidence to deploy software without relying on others to validate it.

Uploaded by

Nitish
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Fast-testing @ Logic Room (mini paper)

Discovering the valuable middle ground


between complexity and productivity.

A Fast-test is neither a unit test, an integration nor an end-2-end test.

A Fast-test is a philosophical test perspective for developing test


automation.

A Fast-test takes the standpoint that we should derive the highest value
from the lowest effort as professionals and avoid work where possible. It
enables engineering teams to avoid ‘handing off’ test automation to a
disjointed ‘test’ team; thus, they can maintain responsibility and control
over the testing themselves.

Its principle is that of Pareto (the 80/20 rule). A Fast-test lets you achieve a
high confidence your app works without the brittleness of end-2-end
testing - in other words it lets a team become lean.

The rules of Fast-testing are…

• They only use a simple unit-testing framework


• The Fast-tests nor the code they test have any dependency on the UI
framework
• They cloak all IO in stubs and spies to make sure they are always
runnable and idempotent - no matter the platform
• They start all testing from the perspective of the user looking inward
into a ‘black box’ of which only input state, process and output state
are visible
• They do not couple to the inside of this ‘black box’ – in this regard
they are uniquely different to ‘unit tests’
• They can scan horizontally and drill vertically through a completely
isolated but connected ‘pure’ JavaScript architecture. They can
deliver testing of 80-90% of the presentation and business logic
concerns in a UI app (called the Fast-test architecture)

By following these 5 rules the implementors of the Fast-test get almost as


high value as integration and end-2-end testing but without the coupling
and brittleness that they provide.

Once a robust Fast-test suite and architecture has been built and is
delivering working software, engineers are encouraged to add integration
and end-2-end testing, judiciously on a case by case basis ‘where needed’.
Thus, deriving an efficient overall approach to testing.

The final principle of the combined effort is one simple mantra; the
engineering team themselves should be confident to safely deploy
without needing to rely upon anyone else to tell them so.

Sound like something you are interested in?

You can learn how to build a Fast-test ready


architecture and test-suite for your UI apps in our…

UI Architecture Academy

You might also like