Today's progress:
- Successfully added code coverage reporting to boxchareditor (using node-cover)
- Added tests to reach 100% line/branch coverage
Still todos:
- Find way to use node coverage report as a job acceptance "test", ie if the code doesn't meet certain minimum coverage, it fails as if a test has failed.
- Find a way to allow someone to test whether their code meets the basic acceptance criteria before the final pull request
Possible ideas about "acceptance/validation tests"
+ Is the github user the one that is allowed to submit the pull request?
+ Is the job still open, within deadline etc?
+ Is the code on a branch?
+ Can the code automatically merge?
+ Test against orginal fork point
+ Test again current head
+ Does the code passes all the unit test
+ Does the code meets the functional acceptance tests?
+ Does the code passes minimum code coverage in testing?
+ avg line,branch coverage, no particular file below certain #
+ Is the code "compliant" (follows stylistic requirements, conventions etc). (jshint config)
+ Are all the dependencies ok
+ dependencies up to date
+ no duplicate dependencies
+ no blacklisted dependencies
+ Does the code passes the browser portability requirement tests.
- Successfully added code coverage reporting to boxchareditor (using node-cover)
- Added tests to reach 100% line/branch coverage
Still todos:
- Find way to use node coverage report as a job acceptance "test", ie if the code doesn't meet certain minimum coverage, it fails as if a test has failed.
- Find a way to allow someone to test whether their code meets the basic acceptance criteria before the final pull request
Possible ideas about "acceptance/validation tests"
+ Is the github user the one that is allowed to submit the pull request?
+ Is the job still open, within deadline etc?
+ Is the code on a branch?
+ Can the code automatically merge?
+ Test against orginal fork point
+ Test again current head
+ Does the code passes all the unit test
+ Does the code meets the functional acceptance tests?
+ Does the code passes minimum code coverage in testing?
+ avg line,branch coverage, no particular file below certain #
+ Is the code "compliant" (follows stylistic requirements, conventions etc). (jshint config)
+ Are all the dependencies ok
+ dependencies up to date
+ no duplicate dependencies
+ no blacklisted dependencies
+ Does the code passes the browser portability requirement tests.
No comments:
Post a Comment