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

Provide public site to run tracker javascript tests #6188

Open
tsteur opened this issue Sep 10, 2014 · 0 comments
Open

Provide public site to run tracker javascript tests #6188

tsteur opened this issue Sep 10, 2014 · 0 comments
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

@tsteur
Copy link
Member

tsteur commented Sep 10, 2014

Many JS frameworks offer the possibility to run their test suite in a browser. So a developer or a user can check whether the framework/lib works with his browser(s). The test result will be sent to the framework developer(s) so they get test results from many browsers without having to do something (of course handling those reports is a lot of effort).

We could offer something similar like a public page where users can execute our tracker test suite '/tests/javascript/' and send us the result including OS, browser version and more. Ideally we would get the result automatically.

@tsteur tsteur added the Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change. label Sep 10, 2014
@tsteur tsteur added this to the Mid term milestone Sep 10, 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
@mattab mattab modified the milestones: Long term, Mid term Dec 5, 2016
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

2 participants