DSpace 6 XMLUI Test Plan
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

 
£
%
123
 
 
 
 
 
 
 
 
 
 
 
 
 
 
ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
Hi, glad to see that you're interested in DSpace 6 XMLUI testing!
2
To get you started, here is the vocabulary you can use to fill out the most important column on the other tabs of this sheet: Test Status
3
4
ValueDescription
5
OK 2014-09-12
When "OK" and a date is entered, the functionality was verified.
6
TEST UNCLEAR
the description of the test doesn't make it clear either what to test, or how a user can test this.
7
FEATURE MISSING
the described functionality couldn't be verified
8
UI PROBLEM
the feature is there and seems to "work", but there is a UI problem (nature of the problem clarified in comments)
9
NON COMPLIANCE
the test fails the expected results
10
DOCUMENTATION
feature seems to work but docs seem to be missing or incomplete
11
12
Now look at the tabs at the bottom of this sheet, to access the tests for specific user personas
13
14
FAQ (in progress - feel free to add questions you may have)
15
16
Which credentials do I use to login to DSpace?
17
Demo.dspace.org features a number of predefined test accounts. They all have the password "dspace", and the email addresses can be found in the homepage intro at http://demo.dspace.org/xmlui
18
19
Can I add tests to the test plan?
20
If you have identified a use case that is currently not covered by other tests, you are certainly invited to add new tests. To do this, just add a row on the corresponding sheet. When doing this, please identify that your test doesn't overlap with another test, and that both the description and expected results are clear.
21
22
What happens after I report a problem?
23
If your test reveals a problem in the codebase, the first step towards resolution is the creation of a JIRA ticket in jira.duraspace.org, where it can be picked up in the developer community. If you don't have a JIRA account, the Role Manager for the test tab on which you reported the problem, will create the JIRA ticket.
24
25
Am I allowed to change test descriptions or expected results?
26
If test descriptions or expected results are unclear, they can definitely be extended or improved throughout the testathon. However, be VERY VERY careful when changing tests that already have a Test Status or linked JIRA tickets. If you change the description or the expected result, that test status or JIRA tickets might not match anymore.
27
28
Where can I execute these tests?
29
You should execute these tests on demo.dspace.org/xmlui. Credentials to login are available on the front page
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
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
Loading...
Main menu