You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
right now the electron-fiddle fake that we have in integration-tests/tests/fixtures/electron-fiddle does a good job of parroting back the right log messages for a given session, but it doesn't parrot the exit code. That's OK in our current integration tests because we're only testing a success path, but it won't work as soon as we test a failure path 🙂
The text was updated successfully, but these errors were encountered:
When running `electron-fiddle bisect`, include arguments to pull in all
of the Electron releases so that the bisection range will be as small as
possible.
Fixes#66 as a side-effect.
* feat: have runner bisect w/obsolete, beta, nightly
When running `electron-fiddle bisect`, include arguments to pull in all
of the Electron releases so that the bisection range will be as small as
possible.
Fixes#66 as a side-effect.
* chore: comment copyediting
* refactor: use electron-fiddle --full
* feat: have runner bisect w/obsolete, beta, nightly
When running `electron-fiddle bisect`, include arguments to pull in all
of the Electron releases so that the bisection range will be as small as
possible.
Fixes#66 as a side-effect.
* feat: support + validate new test tasks in broker
Replaces some very bad broker validation code (of mine) with some new ow
predicates. This includes a TestJob predicate so the broker now supports
both Test and Bisect tasks.
Fixes#110.
* test: add test calling getJob() for an unknown job
* refactor: add JobType enum
* feat: support running individual tests in Runner.
Fixes#104.
right now the electron-fiddle fake that we have in
integration-tests/tests/fixtures/electron-fiddle
does a good job of parroting back the right log messages for a given session, but it doesn't parrot the exit code. That's OK in our current integration tests because we're only testing a success path, but it won't work as soon as we test a failure path 🙂The text was updated successfully, but these errors were encountered: