Understanding part tests and how to create a workflow around them

[akrly]

Hi,

I really like the fact that the test data can be API driven. Basically we can just append our unit tests with short script reducing user input error/etc.

My goal: I would like provide an overview of stock item availability based on test status to my colleagues who create build orders.

Main question: Are test results connected to the business logic in some way? Like failed or incomplete test data would prevent an item from being sold and/or installed.

What we do: We build unit level equipment, which are then built into racks along with commercial units. Test status is vital for us as only tested units can go into the racks.

[SchrodingersGat]

@akrly there are a couple of ways of doing this.

Block Build Until Tests Pass

In the build settings there is an option to block a build output from being "completed" until all tests pass. So, the item under test cannot enter available stock until it has passed all tests

Stock Status

You could manually mark these items with a custom stock status until the tests are passed

Plugins

You could have a custom plugin which could perform an operation on the stock item (e.g. give it a custom status) if a test fails. Basically, the plugin system can respond to any sort of 'events' in the system if the built-in functionality is not sufficient for you

[akrly]

Thanks for the quick reply. Am I correct to understand that if the build output is blocked by the unit tests that stock item is not available to users?

Since the units are built and tested by different people, I think we have to go stock status & plugin route. Thanks again.

[SchrodingersGat]

Am I correct to understand that if the build output is blocked by the unit tests that stock item is not available to users?

Correct, it will be marked as "in production" until the build output is completed