@@ -34,23 +34,30 @@ modular code. Perfect for those looking to speed up their test automation journe
34
34
- headless ` -Drunmode=headless `
35
35
36
36
# CHROME DEVTOOLS PROTOCOL IMPLEMENTATION EXPLAINED
37
+
37
38
** 1. Initialize the CDP Session**
38
- #### What Happens?
39
+
40
+ #### What Happens?
41
+
39
42
- You (the test) ask CdpUtils to start monitoring.
40
43
- CdpUtils tells CDPSessionHandlerImpl to set things up.
41
44
- Playwright provides the tools (CDPSession).
42
45
43
46
![ Initialize_the_CDP_Session] ( https://github.com/user-attachments/assets/b5016da0-1126-4ca4-ad3f-5dd11ff14779 )
44
47
45
48
** 2. Listen for Network Errors**
46
- #### What Happens?
49
+
50
+ #### What Happens?
51
+
47
52
- You ask to log errors (e.g., HTTP 404/500).
48
53
- The CDPSessionHandlerImpl sets up a listener in the browser.
49
54
50
55
![ Listen_for_Network_Errors] ( https://github.com/user-attachments/assets/9406c6cd-d4e5-4cfd-b2b8-789922dbc4e1 )
51
-
56
+
52
57
** 3. Browser Fires an Event**
53
- #### What Happens?
58
+
59
+ #### What Happens?
60
+
54
61
- The browser detects a failed request → notifies CDPSessionHandlerImpl.
55
62
- The error details are passed back to your test (e.g., to log or retry).
56
63
@@ -102,6 +109,25 @@ modular code. Perfect for those looking to speed up their test automation journe
102
109
and with the respective groups and thread counts.
103
110
The screenshot listeners are configured in "pom.xml" under "< property >" tag.
104
111
112
+ #### DECLUTTERING MAVEN OUTPUT
113
+
114
+ - Maven usually floods the console with logs during test execution, making it hard to spot what's important.
115
+ A clean, minimal, Node.js-style output for a Java project felt impossible—until I
116
+ found this [ maven dependency] ( https://mvnrepository.com/artifact/me.fabriciorby/maven-surefire-junit5-tree-reporter ) .
117
+ - Its purpose is simple: ** "What happened to my test cases?"** That’s exactly what it shows—straight to the point, no
118
+ clutter.
119
+ - By following this [ post] ( https://medium.com/wearewaes/my-journey-to-a-clear-test-output-in-maven-df82fe272249 )
120
+ by [ Fabricio] ( https://github.com/fabriciorby ) ,
121
+ I was able to configure it easily and get the clean output shown below.
122
+ - The output works locally and in GitHub Actions as well.
123
+ - Huge respect and thanks to the author for this
124
+ brilliant [ work] ( https://github.com/fabriciorby/maven-surefire-junit5-tree-reporter?tab=readme-ov-file ) !
125
+ ❤️
126
+
127
+ ** Before the Decluttering**
128
+
129
+ ** After the Decluttering**
130
+
105
131
## Star History
106
132
107
133
[ ![ Star History Chart] ( https://api.star-history.com/svg?repos=iamcharankumar/playwright_test_framework&type=Date )] ( https://star-history.com/#iamcharankumar/playwright_test_framework&Date )
0 commit comments