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