Differences between revisions 34 and 35
Revision 34 as of 2011-01-21 14:09:10
Size: 1899
Editor: jrg
Comment:
Revision 35 as of 2011-01-21 14:27:33
Size: 1901
Editor: jrg
Comment:
Deletions are marked like this. Additions are marked like this.
Line 10: Line 10:
|| [[RadioTVStageTestVerifyClipping|Verify that we can clip a media file out from an ingested object]]||to be tested || || || [[RadioTVStageTestVerifyClipping|Verify that we can clip a media file out from an ingested object]]||to be tested.. || ||

STAGE-Test of DOMS RadioTV System

High-level overview of tests in STAGE:

Step

Test succeeded (yes/no)

If no, what went wrong?

Start tomcat - is the DOMS running?

yes (2011-01-20)

Start the ingester - does it run properly?

yes (2011-01-20)

Start the pre-ingester - does it run properly?

to be tested..

Verify that all pre-ingest files have been successfully ingested in the DOMS.

to be tested..

Verify that we can clip a media file out from an ingested object

to be tested..

Verify that the ingested objects can be found by search and played in the web browser

to be tested..

How to count published radioTV program objects in Fedora


The machines used for stage-testing are the folowing:

  • stage01 aka tethys, user doms - used for lowlevelbitstorage

  • stage02 aka helene, user develro - real user fedora - used for digitv and ingester

  • stage05 aka epimetheus, user develro - used for the DOMS-portal aka web frontend

  • debit, user develro, real user summahst - used for doms/summa backend (perhaps frontend as well?)

  • carme, user develro, real user doms - used for the doms testbed

The machines used for internal DOMS test are:

  • alhena, user fedora - DOMS test machine

  • iapetus, user doms or larm - used for tests of BES and Wowza

  • digitv-test-acs, user fedora - used for testing DigiTV

Stage-Test of DOMS RadioTV System (last edited 2011-02-11 10:33:15 by jrg)