-
The test of the title is broken.
This is what is causing the failure of CI/CD too.
https://github.com/oceanmodeling/searvey/blob/4d23de7bd5a9ffe363f5d299e96a5a3bce6bc8ed/.github/workflows/insta…
-
**Is your feature request related to a problem? Please describe.**
A typical test pattern in unittets is
TEST_F(IFDSTaintAnalysisTest, TaintTest_04) {
initialize({PathToLlFiles + "dummy_source…
-
In Robert C. Martin's blog post https://blog.cleancoder.com/uncle-bob/2017/03/03/TDD-Harms-Architecture.html it's mentioned that before 2008, some unit tests written for Fitnesse were fragile.
Cou…
-
There are still several fragile tests that do something like `expect( response.body ).not_to include a_test_string` - this breaks occasionally when the test string is something that crops up in words …
denny updated
4 years ago
-
Currently, when killing a node in the cluster, we expect that the recovery can be done in a fixed interval of time (15s as the following).
https://github.com/risingwavelabs/risingwave/blob/e4b87beb…
-
Currently we have for example the SOGo application embedded as native frame with SSO code injection.
If we keep this instead of implementing a cookie based SSO we need to add tests to check the scr…
-
**Describe the bug**
multiple problems with scene tests:
* scene tests fail because the Asset database location has moved.
* scene tests fail because new assets are emitted by scene files, but the …
-
This failure of the scheduled testing
https://github.com/ACCESS-NRI/access-om2-configs/issues/41
highlights that the scheduled testing doesn't define a version of the tests to run. This makes it…
-
While working on issue #1018 I added a few relevant unit tests. Which caused me to notice the tests are fragile because they assume the wildcard expansion will be in a specific order. But wildcard exp…
-
The release process has a giant bottle neck in the form of going though each of the examples and updating it to the next version of Azle. I had an idea where we parallelize it by spinning each one up …