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.

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

Continuous Integration server improvements #3606

Closed
mattab opened this issue Dec 13, 2012 · 1 comment
Closed

Continuous Integration server improvements #3606

mattab opened this issue Dec 13, 2012 · 1 comment
Labels
c: Tests & QA For issues related to automated tests or making it easier to QA & test issues. Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.

Comments

@mattab
Copy link
Member

mattab commented Dec 13, 2012

Improvement ideas

  • Run code coverage during the tests and produce reports: Generate Code Coverage of Piwik test suite #4224
  • Implement new Webtests to automatically test the installation, update, login. See Write Installer/Updater screenshot tests #2935
  • Run our piwik.js javascript tests on continuous integration server Run Piwik.js javascript tests on continuous integration #4225
  • automated API doc generation for piwik.js tracker
    • jsphpdoc - does some text transformations and feeds the output to phpDocumentor; since it doesn't parse the JS, it doesn't recognize some of the syntactic sugar to define methods. The result is missing the public methods, but includes many private methods.
    • jsdoc-toolkit - uses rhino/java; despite failing miserably (initial output has only three functions: cvt_hex, piwik_log, and piwik_track), it's probably the more promising of the two given its feature set (and usage by other projects). It appears to we have to add more tags as hints...

Created as a followup / summary of the 2 year old ticket #1470

More information about piwik QA: http://piwik.org/qa/

@mattab
Copy link
Member Author

mattab commented Apr 6, 2014

In the last 9 months we have made many changes and improvements to the QA environment. We are using Travis and testing on 3 different php versions, mysqli + PDO Mysql, we have unit tests, integration tests, plugin tests, and also Javascript tracker tests, and Angular JS tests (just starting those ones slowly!).

Well done to the team for their dedication to testing... it's so nice when we manage to develop in TDD style!

More info at http://piwik.org/qa/
And our travis builds: https://travis-ci.org/piwik/piwik

@mattab mattab added this to the Future releases milestone Jul 8, 2014
@mattab mattab added the c: Tests & QA For issues related to automated tests or making it easier to QA & test issues. label Oct 12, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c: Tests & QA For issues related to automated tests or making it easier to QA & test issues. Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.
Projects
None yet
Development

No branches or pull requests

1 participant