-
After #1169 and #1155 and related: we should exercise the history-related code paths more systematically in the test suite
- generate history for these scenarios / a mixture thereof:
- mixture…
-
## Description
Ensure that users receive email notifications for all payment transactions, including successful upgrades, failed payments, and payment confirmation receipts.
## Acceptance Crite…
-
How to reproduce:
config.yaml shold have this scenario
` chaos_scenarios: # List of policies/chaos scenarios to load
- container_scenarios: …
-
# Objective
To manage my storage with great tools and to enjoy the maintenance of a self-managed appliance.
## Resources
* [Great primer on ZFS](https://www.youtube.com/watch?v=lsFDp-W1Ks0)
…
-
If I have multiple feature files and I am running scenarios by specifying the tags. If I do not include the first scenario from any of the feature file then it is being reported as unnamed scenario in…
-
Expected behavior
The statistics should be consistent in console and reports with table-driven-scenario feature enabled
Actual behavior
There is a mismatch in the statistics reported in console a…
-
### 📖 User Story
**As** a host, when my payment fails
**I want** to know that it has failed and be able to resubmit payment on the application confirmation page and on my dashboard
**So that** I ca…
-
**Describe the bug**
An exception occurs when the price field of the domain is `""`(blank characters) during deploy, resulting in the program terminating unexpectedly.
**Branch/Release/Commit Hash…
-
Allow users to specify which HTTP status codes are considered successful or failed responses, making it more adaptable to different scenarios.
-
## Background
As described in https://github.com/CDLUC3/ezid/issues/696, the current EZID queue system relies on daemons and background service scripts to execute tasks asynchronously. While function…