-
I've opened this issue to discuss *after build* smoke tests.
This could be done with travis.yml file
- build docker image from repo after each branch commit/push
- run newly built container
-…
-
### What is happening
We have added files to the demo product with ID 1 (hello kitty). After that, we encountered very weird and hard to understand errors in smoke tests, because locally, everyth…
-
We need some tests writing which will check that the hugo build was successful and the site deploys correctly. This will be used as part of a PR workflow before enabling merges to `main` once complete…
-
### Problem Statement
We want to make sure Sentry UI loads and can perform basic tasks such as logging in across all major browsers:
- Chrome
- Firefox
- Edge
- Safari
### Solution Brainstorm
…
BYK updated
12 months ago
-
Since we've automated updating dependencies via Greenkeeper, we should have another test suite that runs a build and runs simple verifications (such as "does the build work") on it (smoke testing).
-
There have been a few situations where a hydration error caused pages to not render when it hits production. We should create a smoke test to navigate these pages and ensure they, as a minimum, load.
…
-
We should probably fix these.
```
=============================== warnings summary ===============================
../../usr/local/lib/python3.9/site-packages/django/conf/__init__.py:241
/usr/…
-
### Summary
I noticed that some of [our samples](https://github.com/buildpacks/samples) don't work properly with the current version of lifecycle. (i.e. https://github.com/buildpacks/samples/pull/167…
-
It would be nice to have a couple end-to-end tests that verify that the basics work:
1. homepage shows sectors
2. sector page shows some companies
3. organization page shows an organization
pe…
-
I'm doing some gentle code cleanup in `mrjob.examples` right now, and it's a little scary because there aren't any automated tests for examples. Would be nice to know that we can't break our examples …