-
In one of our Intergration test suite we are getting the following Panic in the ReportAfterSuite. Our code for executes but Ginkgo generated code panic. We have over 9 different test suite and this …
-
Hey Amro et. al,
The recent kerfuffle with v0.2.7 could have been prevented if we had some testing in place. I see that you've already created a test substrate based around test:unit and shoulda.
I…
-
I've been working on some tests for our AMIs + services using Serverspec and looking at Kitchen / BATS and others in conjunction with Packer. I'd think the results would have a place here? If so, is h…
-
We should probably at some point overhaul our test suite. Eg it'd be nice to decouple the features from the systems. There could be a list of predefined pwbasis together with some characteristics (met…
-
### Bug Report or Feature Request (mark with an `x`)
```
- [ ] bug report -> please search issues before submitting
- [x] feature request
```
### Desired functionality
I'd like to be able …
-
(long term improvement)
Find a better way to do comprehensive regression testing of Grappa infrastructure. Possible implementation approaches:
- CMake/CTest with existing Boost Unit Test stuff
- CTes…
bholt updated
11 years ago
-
-
We need to decide on which Continuous Integration / automated testing service we'll be using on our repos. The simplest thing to start with is to use Travis CI on our public repos.
For the private…
-
### Use case
It would be very helpful to people who use CESM+DART
if the released versions of CESM have been tested to ensure
that they provide the functionality required by DART,
such as the ab…
-
This epic contains the user stories for regression testing
Justification:
- decrease the risk of regression
- decrease the time spent on 1st / 3rd party support troubleshooting the issues