MARC Validation Testing Approach

Owned by Khalilah Gambrell
Last updated: Jul 10, 2024
2 min read

Reference Environments

MARC Validation – What about non-ECS snapshot?

  • Do we need to define MARC bib and MARC authority validation rules to deploy?

  • Or will snapshot always call fetch with each update?

MARC Validation – What about ECS snapshot?

  • Do we need to define MARC bib and MARC authority validation rules to deploy?

  • Or will snapshot always call fetch with each update?

MARC Validation – What about non-ECS sprint testing?

  • Do we need to define MARC bib and MARC authority validation rules to deploy?

  • Or will it always call fetch with each update?

MARC Validation – What about ECS sprint testing?

  • Do we need to define MARC bib and MARC authority validation rules to deploy?

  • Or will it always call fetch with each update?

 

MARC Validation – UAT approach  

Testing environment 1 - non ECS

  1. No fetch > Ask several community members to test. Test duration: 1-2

  2. Fetch > No customization > Ask several community members to test. Test duration: 1-2 days

  3. One environment – customized bib and authority rules by Spitfire. KG will ask community to provide specs. Test duration: 1 week.

Testing environment 2 – ECS

  1. No fetch across all tenants > Ask several community members to test. Test duration: 1-2 days

  2. Fetch in one tenant but not in central tenant.  Ask several community members to test. Test duration: 1-2 days.

  3. Ask FOLIO community administrators to update rules in at least one tenant and one is the central tenant.

    1. Identify 1-3 libraries to participate. Testing this scenario will take about two weeks and my thought is that we ask libraries to reserve date/time and each library only has 1 day to setup rules and 2-3 days for user testing.

    2. Need to assign a tenant for a community administrator to update and test with.

    3. Test duration: Two Weeks. Give administrator 3-4 days to configure and remaining time for quickMARC testing. 

Potential Bugfest approach

  • Non-ECS environment

    1. Testing > Customized bib and authority rules defined by Spitfire.

  • ECS environment

    1. Ask FOLIO community administrators to update rules in at least one tenant and one is the central tenant. Test duration: One week

    2. Need to assign a tenant for a community administrator to update and test with.

    3. Following week – community members test these rules.

Other scenarios to consider testing

  • Only fetch MARC bib rules.

  • Only fetch MARC authority rules.

  • Anything else?