Repository navigation
development workflow is slow - for eg. no test cases #36
Description
Activity
One thing to do is add some infrastructure for running regular unit tests, e.g. with nodeunit. Something like formatting "tracebacks" is a good candidate for unit tests.
Otherwise having simple testsuite for each supported unit test library, so that I can run them directly within the project, would help. Along with sample log outputs to create better output formatting.
@rahulnwn @dhimil added some repos and workflow for testing all supported frameworks using ruby script for now https://github.com/browserstack/browserstack-runner/compare/testing
Between
npm test(added in #97) andruby tests/test.rbI think this can be closed.does ruby test cases help?
On Fri, Oct 17, 2014 at 4:41 PM, Jörn Zaefferer notifications@github.com
wrote:Between npm test (added in #97
#97) and ruby
tests/test.rb I think this can be closed.—
Reply to this email directly or view it on GitHub
#36 (comment)
.regards
Nakul Aggarwal
www.browserstack.comYes, it does.
but we need more unit test cases, keeping this open will keep reminding us that unit tests are pending, thoughts?
That is a good point, test coverage is still pretty low. Though I don't think keeping this ticket open will help. Instead, when reviewing pull requests, make sure that test coverage is increasing with each change.
:D
On Mon, Oct 20, 2014 at 3:26 PM, Jörn Zaefferer notifications@github.com
wrote:That is a good point, test coverage is still pretty low. Though I don't
think keeping this ticket open will help. Instead, when reviewing pull
requests, make sure that test coverage is increasing with each change.—
Reply to this email directly or view it on GitHub
#36 (comment)
.regards
Nakul Aggarwal
www.browserstack.com
If you've followed the changes and my comments above, continue here: My changes here break the runner of anything that isn't QUnit. Addressing that requires a lot more work and testing with each supported framework. Since there are no unit tests, testing each changes requires a rather slow run of browserstack-runner. Improving the development workflow should therefore have the highest priority, before anything else is addressed, since that will speed everything else up a lot. I have no idea how to do that, though.
Reference: #35