Class FindObsoleteTermsCliTest

java.lang.Object
ubic.gemma.core.util.test.BaseTest5
ubic.gemma.cli.util.test.BaseCliTest5
ubic.gemma.apps.FindObsoleteTermsCliTest
@ContextConfiguration @TestExecutionListeners(value=org.springframework.security.test.context.support.WithSecurityContextTestExecutionListener.class, mergeMode=MERGE_WITH_DEFAULTS) public class FindObsoleteTermsCliTest extends BaseCliTest5

  • Constructor Details

    • FindObsoleteTermsCliTest

      public FindObsoleteTermsCliTest()

  • Method Details

    • resetMocks

      @AfterEach public void resetMocks()
      The ontology mocks are context singletons, so a stubbed failure would otherwise leak into the next test.

    • test

      @Test @WithMockUser public void test() throws TimeoutException
      Throws:
      TimeoutException

    • anOntologyThatFailsToLoadIsSkippedAndTheCheckStillRuns

      @Test @WithMockUser public void anOntologyThatFailsToLoadIsSkippedAndTheCheckStillRuns() throws TimeoutException
      One ontology that cannot load no longer takes the command down: the unified TDB store's lock error stopped fixOntologyTermLabels at ontology 3 of 20 on frink (2026-09-12). The rest load, and the check still runs.
      Throws:
      TimeoutException

    • whenNoOntologyLoadsTheCommandFails

      @Test @WithMockUser public void whenNoOntologyLoadsTheCommandFails() throws TimeoutException
      …but a run where nothing loads fails rather than reporting an empty result as success.
      Throws:
      TimeoutException