7.0 Release Test

Release Test Information

Changes saved
What did you change?  Notify watchers
 

• Previous 6.0 Release Test
• The Netarkivet devel system is  documented at https://kb-dk.atlassian.net/wiki/pages/viewpage.action?pageId=12225230 (DK developers only)
• Bitmagasin GUI: http://netarkiv-aar-bit-master-devel-01.statsbiblioteket.dk:9941/netarkiv-webclient/integrity-service.html
• Release test status: Started 10 Mar 2021
• NetarchiveSuite 7.0 Release Notes: NetarchiveSuite 7.0 Release Notes
• Prepare Release Test Process

  • Run the tests (with proper definitions of TESTX, PORT and MAILRECEIVERS) as follows:

    export VERSION=7.0-RC2
    export TIMESTAMP=$VERSION
    export H3ZIP=$VERSION
    export TESTX=???
    export PORT=807?
    export MAILRECEIVERS=foo@bar.dk
    export DEPLOYCONF=default_deploy_config.xml
    ## OR
    ## export DEPLOYCONF=deploy_config_bitmag.xml
    all_test.sh

    (It is easiest just to copy these commands to a file on kb-prod-udv-001.kb.dk and source the file to start a clean test instance.)

    ViewerProxy Setup

    ViewerProxy is an older part of NetarchiveSuite which can be used for Quality Assurance of http sites (but not https). It is also used within NAS GUI to access files and metadata records. To use ViewerProxy you need to follow two steps

    • Port forward via kb-prod-udv-001.kb.dk to the ViewerProxy instance on kb-test-acs-001.kb.dk. You can do this by running the following command on kb-prod-udv-001.kb.dk: 

      ssh -g -N -L$PORT:kb-test-acs-001.kb.dk:$PORT kb-test-acs-001.kb.dk

    • Set your browser to use kb-prod-udv-001.kb.dk:8078 as a web proxy for http. You should set kb-test-adm-001.kb.dk as an exception to the proxy rule so that you can still browse the NetarchiveSuite GUI and also sbforge.org so you can still browse in this test description.

      Revision-Tag	Commit	Reason for Rejection
      7.0-RC1	4ab01e	Bitmag paths were still hard-coded in the start scripts prepared by the deploy application
      7.0-RC2	e22863f	FileNameHarvester (WaybackIndexer) doesn't reconnect if bitmag is down
      7.0-RC3	191b3f4	(Not rejected but new functionality added to stress-test code)
      7.0-RC4	df4c1ca5

Precondition

Check that the Unit Test Suite and System Test for both Bitmag and ArcRepository deployments are all green.

Sanity test

Run right after code freeze to verify the system integrity prior to the main release test.

Regression tests

Test new functionality (Excluded)

(H3 Scripting features do not need to be tested as part of the NAS release test.)

Review of Documentation

Comments