File: TESTING.md

package info (click to toggle)
rocs 4:20.12.1-1
  • links: PTS, VCS
  • area: main
  • in suites: bullseye, sid
  • size: 7,692 kB
  • sloc: cpp: 14,726; javascript: 784; xml: 598; makefile: 13; sh: 12
file content (122 lines) | stat: -rw-r--r-- 2,766 bytes parent folder | download | duplicates (2)
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
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
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
# Release Testing

**Last Update**: 2012-06-03

This file describes the testing procedures that should be done when releasing 
Rocs. The test procedure starts with a simple checklist (that can be skipped
by beta testers) and then focuses on testing the functional properties
of the application

## Release Checklist

### Release Information

* Application version is bumped
* About Dialog is updated
* Application information updated at edu.kde.org

### Static Code Checkers

* All (important) Krazy issues are fixed:
  http://ebn.kde.org/krazy/reports/kde-4.x/kdeedu/rocs/index.html
* Build issues are fixed:
  https://build.kde.org/job/Applications/job/rocs/

### Unit Tests

* All unit test pass:
  https://build.kde.org/job/Applications/job/rocs/

### Documentation

* Handbook builds
* Handbook is updated

### Website and Release Information

* edu.kde.org is updated
* features are correctly reported at KDE Feature List

## Beta Test Instructions

```
///////////////////////////////////////////////////////////////////////////////
Name of tester:
Date:
OS Version:
Qt Version:
KDE Version:
///////////////////////////////////////////////////////////////////////////////
```

Before starting with the tests you should run the unit test to check whether
your installation is fine.

## Tutorial Tests / Documentation

### T001 - Tutorial

Test procedure:

1. Proceed steps as described in the Rocs tutorial in the handbook.

### T002 - Compare UI elements from handbook with Rocs UI

Test procedure:

1. Look up the User Interface Section in the handbook
2. Compare images and names of UI elements

## Projects

### P001 - Projectfiles

Test procedure:

1. Create two data elements and connect them (data structure shall not be empty).
2. Write "test" into the script file.
3. Save project.
4. Close Rocs.
5. Open Rocs.
6. Load project.

### P002 - Projectfiles with directory change

Test procedure:

1. Create two data elements and connect them (data structure shall not be empty).
2. Write "test" into the script file.
3. Save project to folder foo.
4. Close Rocs.
5. Rename folder foo to baa.
6. Open Rocs.
7. Load project.

### P003 - Export/Import (simple)

Test procedure:

1. Create two data elements and connect them (data structure shall not be empty).
2. Write "test" into the script file.
3. Export project as archive.
4. Close Rocs.
5. Open Rocs.
6. Import archive.

### P004 - Export/Import with directory change

Test procedure:

1. Create two data elements and connect them (data structure shall not be empty).
2. Write "test" into the script file.
3. Export project as archive.
4. Close Rocs.
5. Move archive file to another folder.
6. Open Rocs.
7. Import project.

## Create and Modify Data Structures

## Script Engine

## Script Execution