armi.tests.test_interfaces module¶
Tests the Interface.
- class armi.tests.test_interfaces.DummyInterface(r, cs)[source]¶
Bases:
armi.interfaces.Interface
Construct an interface.
The
r
andcs
arguments are required, but may beNone
, where appropriate for the specificInterface
implementation.- Parameters
r (Reactor) – A reactor to attach to
cs (Settings) – Settings object to use
- Raises
RuntimeError – Interfaces derived from Interface must define their name
- name: Optional[str] = 'Dummy'¶
The name of the interface. This is undefined for the base class, and must be overridden by any concrete class that extends this one.
- function = 'dummyAction'¶
The function performed by an Interface. This is not required be be defined by implementations of Interface, but is used to form categories of interfaces.
- class armi.tests.test_interfaces.TestCodeInterface(methodName='runTest')[source]¶
Bases:
unittest.case.TestCase
Test Code interface.
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.tests.test_interfaces.TestTextProcessor(methodName='runTest')[source]¶
Bases:
unittest.case.TestCase
Test Text processor.
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.tests.test_interfaces.TestTightCoupler(methodName='runTest')[source]¶
Bases:
unittest.case.TestCase
Test the tight coupler class.
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_isConverged()[source]¶
Ensure TightCoupler.isConverged() works with float, 1D list, and ragged 2D list.
Notes
2D lists can end up being ragged as assemblies can have different number of blocks. Ragged lists are easier to manage with lists as opposed to numpy.arrays, namely, their dimension is preserved.