-
I think the latest set of releases have shown some real holes in our testing.
I would propose we setup some automated testing to flash the firmware onto all the appropriate boards and run some tests …
-
A test failed on a tracked branch
```
Error: Timeout of 360000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/opt/buildkite-agent/buil…
-
I think this would not be superfluous, and would have allowed to avoid stupid mistakes in releases.
Example smoke test https://github.com/babel/babel-preset-env/pull/240/commits/8101857b893c99834dc…
-
# 🐛 Summary #
It also looks like the smoke tests need a once over. In particular, the markdown tests reference the wrong location for the baselines and fail on baseline update changes:
## To rep…
-
Investigate and compare smoke testing tools for our web application, focusing on their integration capabilities with our CI/CD pipeline and keep the cost at zero. The goal is to identify the most suit…
-
Scenario: Should fetch n URLs after fresh install/activate
Given: Fresh install of WPR
And: home page have > 10 links
When: activate WPR
And: wait
Then: The 1st n URLs in home + home URL are adde…
-
Tested platforms should include:
- [ ] Fabric
- [ ] Latest Snapshot
- [ ] Latest Release
- [ ] 20.1
- [ ] 18.2
- [ ] 16.5
- [ ] 14.4
- [ ] Legacy Fabric
- [ ] 12.2
- [ ] 8.9
…
Nolij updated
2 months ago
-
https://dev.azure.com/monacotools/Monaco/_build/results?buildId=279265&view=results
1) VSCode Smoke Tests (Electron)
Terminal
Terminal Tabs
should reset the tab name…
-
As mentioned in #3218, we should have smoke tests for the private docker registry on enabled clouds (AWS/GCP/Azure). One challenge is how to host a private registry for the smoke test.
-
As a block node developer
I want the smoke tests to be reliable and consistent in the CI environment.
So that I can know that failures in a smoke test directly relate to my PR changes.
## Request…