SeleniumTests » History » Version 7
Carsten Rose, 28.12.2023 17:25
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 | * Automated Tests - |
||
13 | |||
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 | |||
22 | |||
23 | 3 | Carsten Rose | * Current Shweta 'QFQ learn' and 'Selenium test' is the same: http://webwork20:37091 |
24 | 2 | Carsten Rose | |
25 | 4 | Carsten Rose | * We need a develop site for Shweta (might be the existing one, or a copy of the new QFQ-Test-Application) |
26 | 1 | Carsten Rose | * A 'production' version which is 'QFQ-Test-Application' |
27 | |||
28 | h2. Preparation Tasks together with Enis |
||
29 | |||
30 | 4 | Carsten Rose | * Setup dedicated QFQ test environment for run as automated tests (Check how Marc did it). |
31 | * Debugging & troubleshoot Python/Selenium tests - *make it easier for Shweta to see what is not working and why*. |
||
32 | 1 | Carsten Rose | |
33 | h2. Update QFQ, Typo3, MariaDB and keep the tests up and running |
||
34 | 3 | Carsten Rose | |
35 | * Document how to update the QFQ-Test-Application. |
||
36 | 4 | Carsten Rose | * How does the developer fetch the latest QFQ-Test-Application? |
37 | 3 | Carsten Rose | * Later: Maybe several T3 / QFQ / MariaDB versions. |
38 | |||
39 | h2. Tasks for Shweta |
||
40 | |||
41 | 7 | Carsten Rose | * Categorize Tests. E.g: Form, FormElement, Report, Link, Downloads (create subpages per topic) |
42 | 4 | Carsten Rose | * Define 'test-data': sql file, all tables have the prefix `Data_`, such test-data can be played (and should implizit remove all previous data). |
43 | 7 | Carsten Rose | * Create Wiki Pages for each category (Form, FormElement, Report, Link, Downloads) and write down all tests (one per line) - go through https://qfq.io/doc. |
44 | 2 | Carsten Rose | |
45 | h2. Topics |
||
46 | |||
47 | * Clean Test Environment |
||
48 | |||
49 | * Reproducable T3 QFQ Site |
||
50 | * Reproducable Data |
||
51 | |||
52 | * Definition: What to test |
||
53 | |||
54 | * Form |
||
55 | |||
56 | * Form Save Record |
||
57 | * Form Update Record |
||
58 | * Form Delete Record |
||
59 | * Each individual FormElement |
||
60 | * Dynamic Update |
||
61 | |||
62 | * Report |
||
63 | |||
64 | * Syntax like: head, tail, shead, stail, rbeg, rend, renr, fbeg, fend, althead, altsql |
||
65 | * `... as _link` |
||
66 | |||
67 | * plain link |
||
68 | * link with question dialog |
||
69 | * link with tooltip |
||
70 | * render mode |
||
71 | |||
72 | * Implement Tests |
||
73 | |||
74 | 7 | Carsten Rose | * |