Versions Compared

Version Old Version 3 New Version 4
Changes made by

Khalilah Gambrell

Khalilah Gambrell

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Status

Status
colourYellow
titleIn PROGRESS

Bugfest Dashboard: https://folio-org.atlassian.net/jira/dashboards/10465

...

Ramsons Performance testing: https://folio-org.atlassian.net/issues/?jql=textfields ~ "ramsons " AND project %3D PERF ORDER BY created DESC

Security:

EnvirBonments and Test runs

Bugfest Environment

Test run

Verification environment before Bugfest deployment

OKAPI non-ECS

non-ECS (folio | folio)

https://bugfest-ramsons.int.aws.folio.org/ (managed by Kitfox)

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)

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)

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)

Ramsons Release readiness - What POs can do

Untested/Re-test test cases

  •  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).
  •  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
  •  Attach defects or change test status to Passed/Re-test/Deferred

Triage defects

  •  Review your Jira defects/enhancements daily. If a defect/enhancement must be done for Ramsons, please make it a P1 or P2.
  •  If the issue is not a P1 or P2, then please move to Sunflower and add the label known-issue-ramsons
    •  Consider adding a note in Potential workaround field
    •  Review Ramsons release notes in case additional information should be added

Performance and Load testing

  •  PTF testing seems to behind so if your teams can allocate time to do its own performance or load testing then do it.
  •  Make these issues P1 and P2 if you feel that it is critical to do so.

Migration testing

  •  Ask your teams about migration testing. Are teams doing enough to be ready?
  •  Identify issues that led to previous CSPs and ask teams to test to verify

Release Notes and Features status