Skip to content

Invoke JavaScript tests via CLI #4168

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
Tracked by #3829
ford-at-aws opened this issue Jan 4, 2023 · 1 comment
Closed
Tracked by #3829

Invoke JavaScript tests via CLI #4168

ford-at-aws opened this issue Jan 4, 2023 · 1 comment
Assignees

Comments

@ford-at-aws
Copy link
Contributor

ford-at-aws commented Jan 4, 2023

User story

As example code engineer (internally) and customer (externally), I want a way to recursively execute all tests from a top-level directory using a single command (e.g. a language-specific test framework command, or a collection of commands located in shell script).

Did you say ALL tests?

Yes, but with a caveat: tests that are:

  1. automation-friendly
  2. currently working without intermittent failures.

You can isolate tests that fit the above criteria using tags (see Section 2 in this epic for more tag info).

What is "automation-friendly"?

This refers to tests are can be executed remotely in an Isengard account with no previous setup required. This would include both unit tests and integration tests.

Acceptance criteria

I know this is done when:

  • I can demonstrate that all tests can be executed on your machine from the CLI (verify this) from the top-level.
  • A single test command (or bash script containing tests) can invoke all tests successfully
  • Any updated test steps are updated in the README
@cpyle0819
Copy link
Contributor

This is handled in #4177

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants