Browse Source
* Create testing framework for CLI - Need to add tsconfig for specs to convert module format and add spec dir to output - Use jasmine-ts to test expected dev cycle would be to have two watchers, one for jslib and one for CLI tests. We could add jslib tests to this jasmine config, but it feels wrong to test a submodule * Run prettier * Add tests to build pipeline * Include required package * Add placeholder test * Run prettier * Add nodemon and fix watchpull/2722/head^2
8 changed files with 2194 additions and 98 deletions
@ -1 +1 @@
@@ -1 +1 @@
|
||||
Subproject commit 11e7133aefa4443e07febde9b3add25539ec2287 |
||||
Subproject commit 19bf7c75a369c59328ee602f37570cf1f50f05b6 |
||||
@ -0,0 +1,3 @@
@@ -0,0 +1,3 @@
|
||||
describe("bw", () => { |
||||
it("is a placeholder test"); |
||||
}); |
||||
@ -0,0 +1,4 @@
@@ -0,0 +1,4 @@
|
||||
// tslint:disable-next-line
|
||||
const TSConsoleReporter = require("jasmine-ts-console-reporter"); |
||||
jasmine.getEnv().clearReporters(); // Clear default console reporter
|
||||
jasmine.getEnv().addReporter(new TSConsoleReporter()); |
||||
@ -0,0 +1,7 @@
@@ -0,0 +1,7 @@
|
||||
{ |
||||
"spec_dir": "spec", |
||||
"spec_files": ["**/*[sS]pec.ts"], |
||||
"helpers": ["helpers.ts"], |
||||
"stopSpecOnExpectationFailure": false, |
||||
"random": true |
||||
} |
||||
Loading…
Reference in new issue