Newer
Older
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
Tests scenarios for client
==========================
Scenarios for HAL- on HAL's platform
------------------------------------
The same procedure is used for all tests:
Software Author:
#. prepare content
#. fill out form
#. submit
HAL moderator:
#. review content submitted
#. check metadata fields on HAL
#. validate submission
SWH side:
1. check content in SWH:
- directory was created
- revision was created
- release was created when releaseNotes and softwareVersion was included (new feature!)
- origin corresponds to HAL url
2. check metadata fields on SWH (in revision)
3. check directory
4. check swh-id on HAL
5. check browsability when entering SWH artifact from HAL
6. check vault artifact recreation
7. access deposit's origin from SWH
+-----------+------------------------------------------+----------+-------+-----------------------------------------+
|scenario |test case |data |result |exceptions or specific checks |
+===========+==========================================+==========+=======+=========================================+
|submit code|content: .tar.gz |.zip |success| |
+-----------+------------------------------------------+----------+-------+-----------------------------------------+
|submit code|content: .zip |.tar.gz |success| |
+-----------+------------------------------------------+----------+-------+-----------------------------------------+
|submit code|content: no content |empty |fail |blocked on HAL |
+-----------+------------------------------------------+----------+-------+-----------------------------------------+
|submit code|content: double compression (.zip in .zip)|.zip x 2 |fail |status `failed` on SWH |
+-----------+------------------------------------------+----------+-------+-----------------------------------------+
|submit code|all metadata-single entry |metadata |success|check that all metadata is transmitted |
+-----------+------------------------------------------+----------+-------+-----------------------------------------+
|submit code|multiple entries |metadata |success|languages / authors / descriptions |
+-----------+------------------------------------------+----------+-------+-----------------------------------------+
|new version|new content- same metadata |content |success|check new swh-id in SWH and HAL |
+-----------+------------------------------------------+----------+-------+-----------------------------------------+
|new version|same content- new metadata |metadata | ? |dead angle- doesn't arrives to SWH |
+-----------+------------------------------------------+----------+-------+-----------------------------------------+
|new version|new content-new metadata | C & M |success|check artifacts history in revisions |
+-----------+------------------------------------------+----------+-------+-----------------------------------------+
|submit code+ deposit on another hal platform + C & M +success+ |
+-----------+------------------------------------------+----------+-------+-----------------------------------------+
Past known bugs:
- v2 problem keeps swh-id from first version
- when deposit workers are down- error 500 is returned on HAL without real
explanation (because there is no error on SWH- deposit status stays `deposited`)