| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Status
| Status | ||||
|---|---|---|---|---|
|
Bugfest Dashboard: https://folio-org.atlassian.net/jira/dashboards/10465
...
Bugfest Environment | Test run | Verification environment before Bugfest deployment (Snapshot) |
|---|---|---|
OKAPI non-ECS non-ECS (folio | folio) https://bugfest-ramsons.int.aws.folio.org/ (managed by Kitfox) Environment updates: Join slack channel #bugfest-notify | https://foliotest.testrail.io/index.php?/runs/view/2759&group_by=cases:section_id&group_order=asc&group_id=128 (called Bugfest:R2 2024 Ramsons > Regression - ECS Disabled) | non-ECS (diku_admin | admin) https://folio-snapshot.dev.folio.org/ (managed by DevOps) |
OKAPI ECS ECS (ecs_admin | admin) https://bugfest-ramsons-consortium.int.aws.folio.org/ (managed by Kitfox) Environment updates: TBD | https://foliotest.testrail.io/index.php?/runs/view/2760&group_by=cases:section_id&group_order=asc&group_id=1124 (called Bugfest:R2 2024 Ramsons > Regression - ECS Enabled) | ECS (ecs_admin | admin) https://folio-testing-ecs-snapshot-cs00000int.ci.folio.org/ (managed by Kitfox) |
Eureka ECS ECS (ecs_admin|admin) https://eureka-bugfest-ramsons-consortium.int.aws.folio.org/ (managed by EBSCO FSE) Environment updates: Join slack channel #eureka-bugfest-notify | https://foliotest.testrail.io/index.php?/runs/view/2762&group_by=cases:section_id&group_order=asc&group_id=1124 (called [Eureka] Bugfest:R2 2024 Ramsons > Eureka Regression - ECS Enabled) | ECS (consortium_admin|admin) https://folio-etesting-snapshot-consortium.ci.folio.org/ (managed by Kitfox) |
...
- Ask community to test…or silently nudge community members.
- If they cannot commit to claiming a test ask them to do exploratory tests.
- Allocate time to conduct testing (whether claim tests or conducting exploratory testing). Especially if conduct exploratory testing IF your team's first priority is Eureka ECS
- Even if a test case has been claimed… then take it.
- Ask your development team to help with testing some test cases
- If you have had any bugs with permissions please consider setting up permissions in a way to troubleshoot issues.
- If you have had previous CSPs consider asking community members to conduct exploratory testing of workflows that led to CSPs.
Failed/Blocked test cases
- Review these cases ASAP (see below links)
- OKAPI non-ECS - https://foliotest.testrail.io/index.php?/reports/view/594 (the report only represents status as of December 9 at 8:50 am ET)
- Eureka ECS - https://foliotest.testrail.io/index.php?/reports/view/593 (the report only represents status as of December 9 at 8:50 am ET)
- OKAPI ECS - https://foliotest.testrail.io/index.php?/reports/view/573 (the report only represents status as of December 2 )
- Attach defects or change test status to Passed/Re-test/Deferred
...
- Update release notes as needed
- Change Jira Feature status - Ramsons features dashboard
Do not feel that your development is ready for release?
- Please let Khalilah and Oleksii know ASAP! Current Ramsons GA date is December 16th.
What about LOC environments?
No POs/QAs/Devs will have access to these environments
LOC will be using Eureka ECS so all work should be tested and verified using Eureka ECS snapshot, sprint, and bugfest environments. As a result, POs
- Make sure Eureka ECS snapshot / sprint / bugfest environments are configured to test LC workflows (ex. LCCN de-duplication)
For the time being, LOC pre-validation environment will be updated daily based on Eureka ECS bugfest deployments and PO/QA verification. Eventually the update frequency will change.