armi.reactor.blueprints.tests.test_blueprints module
Tests the blueprints (loading input) file.
- class armi.reactor.blueprints.tests.test_blueprints.TestBlueprints(methodName='runTest')[source]
Bases:
TestCase
Test that the basic functionality of faithfully receiving user input to construct ARMI data model objects works as expected.
Values are hopefully not hardcoded in here, just sanity checks that nothing messed up as this is code has VERY high incidental coverage from other tests.
NOTE: as it stands it seems a little hard to test more granularity with the blueprints file as each initialization is intended to be a complete load from the input file, and each load also makes calls out to the reactor for some assembly initialization steps.
TODO: see the above note, and try to test blueprints on a wider range of input files, touching on each failure case.
Create an instance of the class that will use the named test method when executed. Raises a ValueError if the instance does not have a method with the specified name.
- class armi.reactor.blueprints.tests.test_blueprints.TestBlueprintsSchema(methodName='runTest')[source]
Bases:
TestCase
Test the blueprint schema checks.
Create an instance of the class that will use the named test method when executed. Raises a ValueError if the instance does not have a method with the specified name.
- test_noDuplicateKeysInYamlBlueprints()[source]
Prove that if you duplicate a section of a YAML blueprint file, a hard error will be thrown.
- test_topLevelComponentInput()[source]
Make sure components defined at the top level are loaded.
Components can be loaded either within the block blueprint or on their own outside of blocks. This checks the latter form.
We specified a 3D component in the test input (sphere) so that it has a height and therefore a volume without requiring a parent.