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

[Feature] End-to-end integration tests #275

Closed
arcanis opened this issue Jul 2, 2019 · 1 comment
Closed

[Feature] End-to-end integration tests #275

arcanis opened this issue Jul 2, 2019 · 1 comment
Labels
enhancement New feature or request

Comments

@arcanis
Copy link
Member

arcanis commented Jul 2, 2019

I'm working to integrate a basic daily cron job that would test Yarn with various projects from the ecosystem (Gatsby, Webpack, ESLint, Babel, Jest, etc), in an effort to quickly detect regressions.

I've wrote the pipeline in azure-e2e.yml, but I'm not quite sure how to integrate it with GitHub. In particular, I'd like to open an issue for each job that didn't work and for which a matching issue doesn't already exist (we can use @yarnbot for that). I could use the GitHub API, but I'm not quite sure how to access the status of the jobs from within the Azure Pipeline itself. Does someone have an idea?

cc @zenithworks, I remember you offered to help us integrate the changelog into Azure on the v1 repository, is that also something in your area of expertise? It would be great if Azure could help us validate the sanity of the JS ecosystem 😄

@arcanis arcanis added the enhancement New feature or request label Jul 2, 2019
@arcanis
Copy link
Member Author

arcanis commented Jul 3, 2019

Should be ok! I've hacked my way around: each acceptance test goes through a report.sh indirection, which adds a new entry in a JSON file. This JSON file is then parsed once all the tests have been run, and voilà ✌️

The current tests should run on Gatsby and Create-React-App. I've tried the report system (opening / closing GitHub issues when the problems are detected then resolved) in a vaccum and it seemed to work!

@arcanis arcanis closed this as completed Jul 3, 2019
@arcanis arcanis mentioned this issue Aug 20, 2019
16 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant