Common Issues and Resolutions

Selenium DevTools CDP Error

Issue: When using CDP actions for the network tab, console, and other DevTools features, you may encounter the following error:

common.CustomException: You are using a no-op implementation of the CDP.
The most likely reason for this is that Selenium was unable to find an
implementation of the CDP protocol that matches your browser. Please be
sure to include an implementation on the classpath, possibly by adding a
new (maven) dependency of org.seleniumhq.selenium:selenium-devtools-vNN:4.19.1
where NN matches the major version of the browser you're using.
Build info: version: '4.19.1', revision: 'abe0ee07dc'
System info: os.name: 'Windows 11', os.arch: 'amd64', os.version: '10.0',
java.version: '23.0.1'
Driver info: DevTools Connection

Resolution: This error indicates a compatibility issue between the Selenium version and the Chrome (CDP) version. Check the Selenium version compatibility with the CDP version using the changelog below, and update the Selenium version in your pom.xml accordingly:

https://github.com/SeleniumHQ/selenium/blob/trunk/java/CHANGELOG

Email Trigger Failure in New Jenkins Setup

Issue: After migrating to a new Jenkins environment, the Email Trigger job (via algoReport.exe) fails to send emails, even though the executable runs successfully and Mono is functioning correctly. The same configuration works without issues in the existing (old) Jenkins setup.

Environment: algoReport.exe on the new Jenkins server (old Jenkins server used for comparison).

Symptoms:

• algoReport.exe executes successfully.
• Mono runs correctly.
• Email fails to send with the following error:

Message could not be sent.
Input string was not in a correct format.

System.Int32.Parse(...)
  at algoReport.Program.Main(...)

Root Cause: An SSL certificate problem on the new server prevents emails from being triggered correctly in the new Jenkins environment.

Resolution:

1. Confirmed that the same algoReport.exe configuration works on the old Jenkins server, isolating the issue to the new environment.
2. Investigated the SMTP/email configuration and related parameters used by algoReport.exe.
3. Diagnosed and resolved the underlying SSL certificate issue on the new server.
4. Re-ran the Email Trigger job on the new Jenkins server and confirmed successful execution and email delivery.
5. Scheduled the job for regular execution and confirmed it passed full testing.

AlgoQA Test Case Generation Failure (Java Server Crash)

Issue: After an unplanned VM restart over the weekend, all CMD windows running background services were closed. When the algoQA server was restarted, the Java server failed to start, blocking test case generation entirely.

Environment: algoQA server / Java server. Triggered by an unplanned VM restart followed by a VM OS update.

Symptoms:

• CMD windows running algoQA services were closed after the VM restart.
• On restarting the algoQA server, the Java server failed to start or crashed.
• Test case generation was completely blocked, preventing the team from proceeding with test fixing and execution.

Root Cause: The VM's operating system was updated as part of the restart, which corrupted the existing Java installation. This corruption caused the Java server to crash and prevented it from starting correctly, which in turn blocked algoQA's test case generation functionality.

Resolution:

1. Identified that the Java server had crashed after the VM restart.
2. Traced the cause to a corrupted Java installation resulting from the VM OS update.
3. Reinstalled Java on the VM.
4. Restarted the algoQA server — test case generation resumed working successfully.
5. Confirmed the Java server started without errors after reinstalling Java.
6. Re-ran test case generation in algoQA and confirmed it completed successfully.