1 5 Two questions regarding testing solids Let s say we have

Question

1 5 Two questions regarding testing solids Let s say we have a simple test setup for a solid using `execute solid` ``` import unittest from dagster import execute solid lambda solid lambda solid def add one x return x + 1 class AddOneTest unittest TestCase def test for zero self result = execute solid add one input values= x 0 self assertEqual 1 result output value ``` When I run the test with `unittest` on the command line the standard output of the test is quite extensive continue to read in the thread

Philipp G · Answer

2 5 ``` 2019 10 31 13 25 28 dagster DEBUG ephemeral add one solid pipeline 4573124d 2990 413a 90bb 24b9671d2a04 PIPELINE START Started execution of pipeline ephemeral add one solid pipeline 2019 10 31 13 25 28 dagster DEBUG ephemeral add one solid pipeline 4573124d 2990 413a 90bb 24b9671d2a04 ENGINE EVENT Executing steps in process pid 10455 event specific data = metadata entries pid null 10455 step keys null add one compute x compute 2019 10 31 13 25 28 dagster DEBUG ephemeral add one solid pipeline 4573124d 2990 413a 90bb 24b9671d2a04 STEP START Started execution of step x compute solid = x solid definition = x step key = x compute 2019 10 31 13 25 28 dagster DEBUG ephemeral add one solid pipeline 4573124d 2990 413a 90bb 24b9671d2a04 STEP OUTPUT Yielded output result of type Any Type check passed event specific data = intermediate materialization null step output handle x compute result type check data true result null solid = x solid definition = x step key = x compute 2019 10 31 13 25 28 dagster DEBUG ephemeral add one solid pipeline 4573124d 2990 413a 90bb 24b9671d2a04 STEP SUCCESS Finished execution of step x compute in 0 48ms event specific data = duration ms 0 48067804891616106 solid = x solid definition = x step key = x compute 2019 10 31 13 25 28 dagster DEBUG ephemeral add one solid pipeline 4573124d 2990 413a 90bb 24b9671d2a04 STEP START Started execution of step add one compute solid = add one solid definition = add one step key = add one compute 2019 10 31 13 25 28 dagster DEBUG ephemeral add one solid pipeline 4573124d 2990 413a 90bb 24b9671d2a04 STEP INPUT Got input x of type Any Type check passed event specific data = input name x type check data true x null solid = add one solid definition = add one step key = add one compute 2019 10 31 13 25 28 dagster DEBUG ephemeral add one solid pipeline 4573124d 2990 413a 90bb 24b9671d2a04 STEP OUTPUT Yielded output result of type Any Type check passed event specific data = intermediate materialization null step output handle add one compute result type check data true result null solid = add one solid definition = add one step key = add one compute 2019 10 31 13 25 28 dagster DEBUG ephemeral add one solid pipeline 4573124d 2990 413a 90bb 24b9671d2a04 STEP SUCCESS Finished execution of step add one compute in 0 44ms event specific data = duration ms 0 4425259539857507 solid = add one solid definition = add one step key = add one compute 2019 10 31 13 25 28 dagster DEBUG ephemeral add one solid pipeline 4573124d 2990 413a 90bb 24b9671d2a04 ENGINE EVENT Finished steps in process pid 10455 in 2 32ms event specific data = metadata entries pid null 10455 step keys null add one compute x compute 2019 10 31 13 25 28 dagster DEBUG ephemeral add one solid pipeline 4573124d 2990 413a 90bb 24b9671d2a04 PIPELINE SUCCESS Finished execution of pipeline ephemeral add one solid pipeline Ran 1 test in 0 071s OK ```

Philipp G · Answer

3 5 I am suppressing this by setting the the log level of the solid to critical when it gets executed but it feels kind of wrong ``` import unittest from dagster import execute solid lambda solid lambda solid def add one x return x + 1 class AddOneTest unittest TestCase def setUp self self silent config = loggers console config log level CRITICAL def test for zero self result = execute solid add one input values= x 0 environment dict=self silent config self assertEqual 1 result output value ```

Philipp G · Answer

4 5 Also it gets a little bit weird when the solid itself also needs to be configured My current way of handling this is creating a new config dict that gets the log level from the setup config ``` import unittest from dagster import Field execute solid solid solid config= add more Field int is optional=True default value=0 def add one context x return x + 1 + context solid config add more class AddOneTest unittest TestCase def setUp self self silent config = loggers console config log level CRITICAL def test for zero self result = execute solid add one input values= x 0 environment dict=self silent config self assertEqual 1 result output value def test add more to zero self test config = loggers self silent config loggers solids add one config add more value 1 result = execute solid add one input values= x 0 environment dict=test config self assertEqual 2 result output value ```

Philipp G · Answer

5 5 I do not have any problem with these solutions but both setting log level to `CRITICAL` to silence output and the way I merge the `silent config` with the `test config` feel a bit weird Does anyone have a better suggestion here This may be a very specific problem with `unittest` and not occurr in other testing modules like `pytest`

alex · Answer

Hmm interesting pytest surpress stdout stderr by default Does using the ` b` option for unittest not work for you <https docs python org 2 library unittest html cmdoption unittest b>

alex · Answer

If that doesn t work for you we could consider something like environment variables that change the default logging behavior

max · Answer

what s nice about pytest is it will suppress stdout for tests that pass and show it for tests that fail

alex · Answer

looks like thats what the ` b` flag for `unittest` does as well

Philipp G · Answer

Yes the ` b` works here I didn t think of it I also can t see any reason not to use it here Thank you for the suggestion