Unit Testing Fuses

If we were all perfect programmers, we'd never need to test. Unfortunately we're not perfect which is why we can make use of unit testing our fuses. The concept of unit testing a fuse is to validate whether it works on it's own. Not only does it run on its own, but does it also produce the desired output?

This is another reason why Fusedocs are so powerful. The important part of Fusedocs is the <io> section. This area tells us what variables the fuse will be given and what variables the fuse needs to create.

For example, it's possible to test a display fuse without a database. Even if the display fuse is displaying records from the database. All we need to know are what <in> variables the fuse will be given. If the fuse will be given a recordset, we simply need to simulate that incoming recordset so we can see what happens when that data comes in.

This is the case for any incoming variable. We can fake each incoming variable to simulate how the fuse will react to different incoming variables. As a tester we need to make a decision whether it's reacting properly or not.

This where the <out> variables come into play. Using fusedocs it's possible to validate whether the data being produced by the fuse matches up with the necessary <out>data in the fusedoc.

Once the fusedocs have been tested to produce the desired output according to the fusedoc, the architect plugs the fuses back into the fuseactions.

Tools

Coming Soon
To help develop new Lasso Fusebox tools please contact us.

Copyright ©2017 LassoFusebox, All Rights Reserved.

Download from GitHub

Contact Us