Class RawExpressionDataWriterCliTest

java.lang.Object
ubic.gemma.core.util.test.BaseTest5
ubic.gemma.cli.util.test.BaseCliTest5
ubic.gemma.apps.RawExpressionDataWriterCliTest
@ContextConfiguration @TestExecutionListeners(value=org.springframework.security.test.context.support.WithSecurityContextTestExecutionListener.class, mergeMode=MERGE_WITH_DEFAULTS) @DirtiesContext(classMode=BEFORE_EACH_TEST_METHOD) public class RawExpressionDataWriterCliTest extends BaseCliTest5
getRawDataMatrix -stdout: every result reaches the standard output, and a write that fails is an error.

Each test gets a fresh CLI bean: the options it has parsed stay in fields that nothing clears.

  • Constructor Details

    • RawExpressionDataWriterCliTest

      public RawExpressionDataWriterCliTest()

  • Method Details

    • setUp

      @BeforeEach public void setUp() throws IOException
      Throws:
      IOException

    • testEveryQuantitationTypeReachesTheStandardOutput

      @Test @WithMockUser public void testEveryQuantitationTypeReachesTheStandardOutput()
      🛑 The second QT reaches the standard output. The writer over it was closed by try-with-resources, which closed the standard output, so with -allQts every QT after the first went into a closed PrintStream and was still reported as written.

    • testAFailedWriteToTheStandardOutputFailsTheRun

      @Test @WithMockUser public void testAFailedWriteToTheStandardOutputFailsTheRun()
      🛑 A write to the standard output that fails (closed pipe, full disk) is an error. PrintStream records it in a flag nothing read, so the run exited 0 having written nothing.