title: Is it even possible to delay or call explicitly a teardown method of a child test case in Katalon Studio?
body: <p>I am testing this site for concierge medical professionals, written in Zoho.</p>
  <p>The flow, of the section in question, is as follows:</p>
  <p>once practice is created, user is to:</p>
  <ol>
  <li>create practice contract</li>
  <li>create rate card for that contract</li>
  <li>create any discounts to apply to that rate card</li>
  <li>create any retainer schedules</li>
  </ol>
  <p>Right now, I have the practice contract and rate card test suites completed, and parameterized/sanity test cases for the discount and retainer schedule test suites. Neither is deterministic right now, as both of those require one &quot;free&quot; rate card, and right now, there's no control for that in the test cases like there is in the rate card test cases.</p>
  <p>The rate card test case has, as its initial/teardown steps, logic to create dummy contract if there isn't a &quot;free&quot; contract to assign the rate card to, and we delete the dummy contract if one had to be created:</p>
  <pre><code>// creating dummy contracts iff there is less than 1 unassigned contract. Else if there are more, we fail the test right away, because that would require us choose one, which is not, by definition a sanity test case concern.
  PracticePage initPage = new PracticePage(practiceProfile.getPracticeURL());
  
  if (!hasUnassignedContract()) {
      createDummyContract()
      
      WebUI.verifyEqual(initPage.getNumberOfContracts(), initPage.getNumberOfRateCards() + 1)
  }
  
  @TearDown
  void close() {
      if (PracticePage.NewContractsCreated &gt; 0) {
          PracticePage page = new PracticePage(((PracticeProfile)practiceProfile).getPracticeURL());
          page.go(); 
          page.deleteFirstContract();
      }
  }
  </code></pre>
  <p>Discount and retainer schedule test cases, since they require a rate card to work off of, should:</p>
  <ol>
  <li>hit up the rate card child test case if the number of discounts/retainer schedules is equal to the number of rate cards, and then</li>
  <li>delete any dummy contract that had to be created afterwards (as we are either completing the practice setup, or adding new info just to test that part of the app)</li>
  </ol>
  <p>but wait a minute, the contract deletion logic happens in the child test case, which means that the contract is going to be deleted once child test case is done!</p>
  <p>How can we either:</p>
  <ul>
  <li>delay that teardown until after the drive test case is done, or</li>
  <li>call that teardown method from the drive test case on done</li>
  </ul>
  <p>?</p>