SeleniumTests » History » Version 4
Carsten Rose, 28.12.2023 17:22
1 | 1 | Carsten Rose | h1. SeleniumTests |
---|---|---|---|
2 | 2 | Carsten Rose | |
3 | * *Test QFQ* |
||
4 | * Test a specific application |
||
5 | |||
6 | |||
7 | * *Interactive Tests* - used during developing of selenium tests |
||
8 | * Automated Tests - |
||
9 | |||
10 | 4 | Carsten Rose | h2. QFQ-Test-Application |
11 | 1 | Carsten Rose | |
12 | 3 | Carsten Rose | * Creating a dedicated QFQ-Test-Application (#17523) - this will be the base for all further interactice and automated tests. |
13 | 4 | Carsten Rose | * This will be the same for a) Developer (check out new features, example code) and b) selenium tests. |
14 | 1 | Carsten Rose | * The 'Develop' part will be based on the crose QFQ site http://webwork20:38773/ |
15 | 4 | Carsten Rose | * Selenium Test Data: all tables start with 'Data_' |
16 | * Developer Test Data: all tables start with 'Dev_' |
||
17 | |||
18 | |||
19 | 3 | Carsten Rose | * Current Shweta 'QFQ learn' and 'Selenium test' is the same: http://webwork20:37091 |
20 | 2 | Carsten Rose | |
21 | 4 | Carsten Rose | * We need a develop site for Shweta (might be the existing one, or a copy of the new QFQ-Test-Application) |
22 | 1 | Carsten Rose | * A 'production' version which is 'QFQ-Test-Application' |
23 | |||
24 | h2. Preparation Tasks together with Enis |
||
25 | |||
26 | 4 | Carsten Rose | * Setup dedicated QFQ test environment for run as automated tests (Check how Marc did it). |
27 | * Debugging & troubleshoot Python/Selenium tests - *make it easier for Shweta to see what is not working and why*. |
||
28 | 1 | Carsten Rose | |
29 | h2. Update QFQ, Typo3, MariaDB and keep the tests up and running |
||
30 | 3 | Carsten Rose | |
31 | * Document how to update the QFQ-Test-Application. |
||
32 | 4 | Carsten Rose | * How does the developer fetch the latest QFQ-Test-Application? |
33 | 3 | Carsten Rose | * Later: Maybe several T3 / QFQ / MariaDB versions. |
34 | |||
35 | h2. Tasks for Shweta |
||
36 | |||
37 | 4 | Carsten Rose | * Categorize Tests. E.g: Form, FormElement, Report, Downloads (create subpages per topic) |
38 | * Define 'test-data': sql file, all tables have the prefix `Data_`, such test-data can be played (and should implizit remove all previous data). |
||
39 | * Create Wiki Pages for each category (Form, FormElement, Report, Downloads) and write down all tests (one per line) - go through |
||
40 | 2 | Carsten Rose | |
41 | h2. Topics |
||
42 | |||
43 | * Clean Test Environment |
||
44 | |||
45 | * Reproducable T3 QFQ Site |
||
46 | * Reproducable Data |
||
47 | |||
48 | * Definition: What to test |
||
49 | |||
50 | * Form |
||
51 | |||
52 | * Form Save Record |
||
53 | * Form Update Record |
||
54 | * Form Delete Record |
||
55 | * Each individual FormElement |
||
56 | * Dynamic Update |
||
57 | |||
58 | * Report |
||
59 | |||
60 | * Syntax like: head, tail, shead, stail, rbeg, rend, renr, fbeg, fend, althead, altsql |
||
61 | * `... as _link` |
||
62 | |||
63 | * plain link |
||
64 | * link with question dialog |
||
65 | * link with tooltip |
||
66 | * render mode |
||
67 | |||
68 | * Implement Tests |
||
69 | |||
70 | * |