krakenjs/nemo

Issues

• Multiple driver instances are not stable

  #122 opened 2 years ago by Noyabronok
  0

• Latest mochaawesome[6.2.2] wanted

  #110 opened 3 years ago by zzhengjian
  0

• describe.skip is not working as expected

  #74 opened 3 years ago by macropace
  2

• Feature Request: Ability to exclude certain tags while running tests.

  #104 opened 4 years ago by sohamashodiya
  0

• The scaffold feature is broken in nemo@4.12

  #100 opened 4 years ago by grawk
  2

• An in-range update of async is breaking the build 🚨

  #84 opened 5 years ago by greenkeeper
  2

• An in-range update of graphql is breaking the build 🚨

  #86 opened 5 years ago by greenkeeper
  1

• An in-range update of minimist is breaking the build 🚨

  #90 opened 5 years ago by greenkeeper
  5

• An in-range update of flatted is breaking the build 🚨

  #92 opened 5 years ago by greenkeeper
  1

• An in-range update of eslint is breaking the build 🚨

  #81 opened 5 years ago by greenkeeper
  1

• Some profiles missed when launch multiple cases in one nemo command

  #79 opened 5 years ago by kevinx701
  0

• Can we have a switch for zero exit code when tests fail

  #59 opened 5 years ago by zzhengjian
  4

• Orphaned *driver processes

  #63 opened 6 years ago by grawk
  0

• Load plugins in earlier phase.

  #60 opened 6 years ago by mengchen2
  2

• destroyNemo not properly called in Suite.afterAll in mocha.js

  #57 opened 6 years ago by LucasMaupin
  4

• Regression in 4.9.1 with merged profiles?

  #56 opened 6 years ago by smitch88
  2

• Parallel by data: nemo.data merges data from top-level keys

  #32 opened 6 years ago by dwbruhn
  6

• Plain JS config no longer merges top-level data

  #52 opened 6 years ago by dwbruhn
  0

• Plain JS config: How to load plugins?

  #53 opened 6 years ago by dwbruhn
  3

• Improvements (suggestions)

  #48 opened 6 years ago by danielsoner
  3

• duration is null in summary.json file

  #12 opened 6 years ago by grawk
  2

• kill instances where zero tests are matched

  #13 opened 6 years ago by grawk
  1

• Is there a way to know how many tests are going to run before tests start running.

  #43 opened 6 years ago by sainianubhav
  3

• documentation wrong about `nemo.snap`

  #45 opened 6 years ago by grawk
  1

• Is this known feature or a bug?

  #37 opened 6 years ago by sainianubhav
  2

• Things that I think we can improve upon in code.

  #44 opened 6 years ago by sainianubhav
  1

• http://nemo.js.org/pages/ecosystem.html is not in navigation

  #36 opened 6 years ago by sainianubhav
  1

• Screenshot 'on exception' doesn't work on nemo@^4

  #33 opened 6 years ago by ruslK
  2

• What do you mean parallel?

  #35 opened 6 years ago by sainianubhav
  1

• option to quit driver after every test - it()

  #3 opened 6 years ago by sairamnutheti
  3

• Able to support multiple reporters

  #15 opened 6 years ago by mengchen2
  1

• custom CLI args not available in parallel mode

  #21 opened 7 years ago by grawk
  0

• Support CLI option `exit` to force exit after mocha done running the tests

  #29 opened 6 years ago by sairamnutheti
  4

• Nemo exits with status code 0 even for failing tests

  #24 opened 6 years ago by sairamnutheti
  1

• differentiate nemo stdout summary table

  #16 opened 7 years ago by grawk
  0

• Make sure this.nemo available in all mocha lifecycle functions

  #19 opened 7 years ago by grawk
  1

• [Feature] Default logging behavior

  #2 opened 7 years ago by maxuuell
  6

• express uninstalled if --save=dev

  #1 opened 7 years ago by grawk
  1

• Dynamically generating tests

  #10 opened 7 years ago by sairamnutheti
  3