You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/pages/features/e2e_testing.mdx
+1-1
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ The E2E UI Testing feature is designed to streamline the process of creating and
27
27
28
28
5.**Continuous Integration**: As the web application evolves, the feature can regenerate or update the test scripts to ensure they remain aligned with the latest changes and requirements.
29
29
30
-
You can find an example [here](https://github.com/Cloud-Code-AI/kaizen/tree/main/examples/basic)
30
+
You can find an example [here](https://github.com/Cloud-Code-AI/kaizen/tree/main/examples/e2e_test)
Copy file name to clipboardexpand all lines: kaizen/llms/prompts/ui_tests_prompts.py
+22-2
Original file line number
Diff line number
Diff line change
@@ -1,25 +1,45 @@
1
-
UI_MODULES_PROMPT="""
1
+
E2E_MODULES_PROMPT="""
2
2
Assign yourself as a quality assurance engineer.
3
3
Read this code and design comprehensive tests to test the UI of this HTML.
4
4
Break it down into 5-10 separate modules and identify the possible things to test for each module.
5
5
For each module, also identify which tests should be checked repeatedly (e.g., after every code change, every build, etc.).
6
6
7
7
Return the output as JSON with the following keys:
8
+
{{"tests": {{
9
+
"id": "serial number to identify module",
10
+
"module_title": "title of the identified module",
11
+
"tests": [
12
+
{{
13
+
"id": "serial number for the test case",
14
+
"test_description": "description of the test case",
15
+
"test_name": "name of the test case",
16
+
"repeat": true,
17
+
"reason": "reason to add this test",
18
+
}},
19
+
...
20
+
],
21
+
"folder_name": "relevant name for the module",
22
+
"importance": "critical"
23
+
}}
24
+
}}
25
+
26
+
Details:
8
27
id - serial number to identify module
9
28
module_title - title of the identified module
10
29
tests - JSON containing list of tests steps to carry out for that module with keys:
11
30
id - serial number for the test case
12
31
test_description - description of the test case
13
32
test_name - name of the test case
14
33
repeat - boolean indicating if this test should be checked repeatedly or not
34
+
reason - reason to add this test case
15
35
folder_name - relevant name for the module
16
36
importance - level of importance of this test out of ['critical', 'good_to_have', 'non_essential']
17
37
18
38
Share the JSON output ONLY. No other text.
19
39
CONTENT: ```{WEB_CONTENT}```
20
40
"""
21
41
22
-
UI_TESTS_SYSTEM_PROMPT="""
42
+
E2E_TESTS_SYSTEM_PROMPT="""
23
43
You are a Quality Assurance AI assistant specializing in writing Playwright test scripts for web applications. Your goal is to create robust and maintainable test scripts that can be integrated into a CI/CD pipeline.
24
44
25
45
When given requirements or specifications, you should:
0 commit comments