Release Test Information
- Previous 4.4 release test
- Release test status: Planned start 15.05.2015
- NetarchiveSuite 5.0-Milestone1 change notes.
- Setup DK test environment
- Prepare Release Test Process
Run right after code freeze to verify the system integrity prior to the main release test.
|made changes to the netarkivet urls used because of website changes; disabled SB HIGHPRI harvester as it didn't have access to the clock|
After the release test has finished and any critical bugs found have been fixed, a beta release will be made
Run through the Quick Start Manual
Ran into NAS-2434 Unable to access the H3 GUI in quickstart. Unable to reproduce the problem for the fully deployed system.
(Only critical bug is (NAS-2423)
This bug is now fixed
Found NAS-2419 (java.lang.IllegalStateException: STREAM are thrown by Jetty). Step 3 - global crawlertrap fails due to this bug
The errormessage shown to the user in step 5 is very wide: The text: dk.netarkivet.common.exceptions.IllegalState: Cannot make domain 'dbc.dk' an alias of 'netarkivet.dk', as that domain is already an alias of 'kb.dk'
is shown as one(!) line
Overrides in H3 is done with sheets, and is done either with scripting and editing of the configuration in the gui. (See NAS-2422). The screenshots in TEST2 is for h1, not for h3
Heritrix3 instances is not stopped when the harvestcontrollerApplication is shut down. (NAS-2423)
|Done||Only minor changes to the test description needed. However the remote SSH commands with $TESTX in the commands failed to work, as did the upload command, see the comments on TEST3A|
Danish ADM GUI Access, indexing and caching
found bug NAS-2416, and NAS-2417 Firewall issues made it necessary to use a browser on kb-test-adm-001.kb.dk for the proxying
Scripts from CVS on kb-prod-udv-001.kb.dk modified to suit the new testing environment. Se comments on TEST5A
The JMS broker stop and start part of the test was done using a Quickstart setup. It was discussed on Hipchat, that this part should be moved to TEST0. The rest of TEST5B should maybe be added to TEST5A
Errorhandling (Robustness test)
(Network recovery test postponed)
Run in the future as part of TEST0
Database crash test, Network recovery test
Tests that the system can survive a network crash/stop and resume operation after the becomes available
Realised today, that this test should be rerun after NAS-2423 is fixed and reviewed
Has run the test today until the restart, and it works. However the h3-instances on kb-test-har-003 and 004 was still running when the system was started again. Other than that the system worked as expected.
The page http://dia-prod-udv-01.kb.dk:8074/BitPreservation/Bitpreservation-filestatus.jsp was unresposive at first when restarting the database (it hang for quite a while)
Production load job schedule database, adminDB and CS
The automated version of this test now passes.
half of the steps in TEST9 cannot be done, as the folder /home/test/test-data is missing from kb-prod-udv-001.kb.dk
With NAS-5.0 more logging seems to be output to the screen, making it difficult to sort logging from output to STDOUT/STDERR from the batch program.
The batchprogs and lib/jhove folder were taken from email@example.com:/home/test/backup/iteration52/TEST11A/
Batchjobprocessing stress test with external program
The machine used in this test with the 14TB is not ready.Needs java8 and user ba-devel. Possibly this test could be part of the accept test instead of the releasetest
|After CSR updated the test-description, the test now is completed||Søren|
scripts from test@kb-test-way-001 to devel@kb-test-way-001; deploy_test12_wayback.sh not found on firstname.lastname@example.org
derbyrun-10.10.1.1.jar is not part of the libraries in NAS-5.0 distribution (needed by database start/stop scripts on kb-testway-001)
Derby-start and stop scripts does not work with java-8. Work-around: started derby with java-6 instead. Java-7 will probably also work) But they are not needed, as all tests on email@example.com use the same derby server listening to port 50002
Same as French UI test?
German UI test
Test new functionality