Skip to content
New issue

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

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Jump to bottom

discussion: testing organization discussion #93

Open
7 of 12 tasks
dsebastien opened this issue Mar 2, 2018 · 0 comments
Open
7 of 12 tasks

discussion: testing organization discussion #93

dsebastien opened this issue Mar 2, 2018 · 0 comments
Labels
comp: testing effort: days must type: discussion / RFC
Milestone
must

Comments

@dsebastien
Copy link
Contributor

dsebastien commented Mar 2, 2018 •
edited by SuperITMan
Loading

Let's discuss how to tackle all of our and our users testing needs.

Add everything you can think of to this list:

  • root: execute all unit tests from stark's root (e.g., before a release)
  • root: execute all integration/e2e tests from stark's root (e.g., before a release)
  • root: generate code coverage reports from stark's root)
  • specific stark package (e.g., stark-core): execute unit tests
  • specific stark package (e.g., stark-core): execute integration/e2e tests
  • specific stark package (e.g., stark-core): generate code coverage reports
  • stark-build: execute unit tests
  • stark-build: execute integration/e2e tests
  • stark-build: generate code coverage reports
  • showcase: support for e2e testing
  • stark-testing: isolate testing specific tooling in a separate package
  • travis reporters

Related: #73, #68, #82, #84
@dsebastien dsebastien added this to the 10.0.0-alpha.1 milestone Mar 2, 2018
@dsebastien dsebastien changed the title testing: organization discussion discussion: testing organization discussion Mar 5, 2018
@dsebastien dsebastien modified the milestones: 10.0.0-alpha.1, sprint 1 Mar 19, 2018
christophercr referenced this issue in christophercr/stark Mar 22, 2018
@christophercr
feat(stark-testing): create separate stark-testing package. Replace t…
0bbcc9d 
…esting specific dependencies by stark-testing in all stark packages and starter. Fixes #68. [#68][#84][#93]
@christophercr christophercr mentioned this issue Mar 22, 2018
Merged
3 tasks
dsebastien pushed a commit that referenced this issue Mar 23, 2018
@christophercr @dsebastien
feat(stark-testing): create separate stark-testing package and use it…
204dc35 
… in all stark packages and starter (#267)

* feat(stark-testing): create separate stark-testing package. Replace testing specific dependencies by stark-testing in all stark packages and starter. Fixes #68. [#68][#84][#93]

* chore(stark-testing): upgrade dependencies in stark-testing package. Upgrade @types/node in all packages

* fix(stark-testing): downgrade 'jasmine-core' dependency due to an issue with Zone.js (angular/zone.js#1015)

* fix(starter): clean up tsconfig.spec.json for unit testing
dsebastien pushed a commit that referenced this issue Mar 23, 2018
@christophercr @dsebastien
fix(http): fix unit tests. Enhance http demo in Starter (#268)
6d609b8 
* feat(stark-testing): create separate stark-testing package. Replace testing specific dependencies by stark-testing in all stark packages and starter. Fixes #68. [#68][#84][#93]

* chore(stark-testing): upgrade dependencies in stark-testing package. Upgrade @types/node in all packages

* fix(stark-testing): downgrade 'jasmine-core' dependency due to an issue with Zone.js (angular/zone.js#1015)

* fix(starter): clean up tsconfig.spec.json for unit testing

* fix(http): fix unit tests. Enhance http demo in Starter [#96]
@dsebastien dsebastien added the P1 label Apr 24, 2018
@dsebastien dsebastien modified the milestones: sprint 1, 10.0.0-alpha.4 May 8, 2018
@dsebastien dsebastien modified the milestones: 10.0.0-alpha.6, must Aug 1, 2018
@dsebastien dsebastien added P2 and removed P1 labels Aug 1, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
comp: testing effort: days must type: discussion / RFC
Projects
None yet
Milestone
must
Development

No branches or pull requests
2 participants
@dsebastien @christophercr