this.exit(0) no longer exits in v3 about core HOT 3 CLOSED

@mdonnalley thanks for restoring the exit behavior! I noticed in your PR that you're using .catch(/EEXIT: 0/) in your tests. Is it possible to use .exit(0) instead for more consistency between the command and test (i.e., the command calls this.exit so my test would verify that with test.exit)?

maxbeatty/reproduce-oclif-test-exit-zero#7 is upgrading to the newest version of @oclif/test but failing because I am using .exit(0)

https://github.com/maxbeatty/reproduce-oclif-test-exit-zero/blob/0aca49ec6fb0d1180aef4ca391e8885bec2390ee/test/commands/hello/index.test.ts#L14

https://github.com/maxbeatty/reproduce-oclif-test-exit-zero/blob/0aca49ec6fb0d1180aef4ca391e8885bec2390ee/test/commands/hello/index.test.ts#L29

from core.

@maxbeatty Yes, it is possible. Those test are, for some unknown reason, using fancy-test directly instead of @oclif/test, which is what exposes the .exit option.

If I had rewritten it to use @ocilf/test it would have looked like this:

import {test} from '@oclif/test'

test
  .stdout()
  .do(() => {
    class Command extends Base {
      async run() {
        this.exit(0)
      }
    }

    return Command.run([])
    })
  .exit(0)
  .it('exits with 0')

from core.

apologies for the oversight on my end. this is all working as expected now. thank you!

maxbeatty/reproduce-oclif-test-exit-zero@532581b

from core.