Hi,
> We will likely need to escalate this to Smartbear.
This is definitely a good idea and I will appreciate it if you update this thread with their reply. Use https://support.smartbear.com/testcomplete/message/ form to create Support ticket.
> it seemed like the DevTools page uses the protocol, so I assumed one meant the other.
I am not sure. My personal understanding is that CDP is just a communication protocol (with the Chromium engine). DevTools uses CDP to talk to browser, but implements additional functionality on top of raw data provided by the engine via CDP. Just like Selenium, for example. Selenium library communicates with the code injected into web page via its protocol, but provides additional functionality via its object model.
> How does TestComplete know which port to access CDP?
Based on the referenced help topic I understand it this way:
-- You must specify the --remote-debugging-port=<port_number> parameter for the applications started using command line. I believe that TestComplete parses command line of the tested application when connects to it (to the application) and thus obtains port number;
-- You must specify the -cdpAutoSetPort command-line parameter for applications started as TestedApps from TestComplete. Again, I believe that in this case TestComplete also has access to all required information.
> How do I know that the CDP is running / accessible?
Not sure I got the question. If you like to ensure that CDP is accessible to TestComplete, you, probably, need to go through CDP documentation.
If you like to know whether TestComplete works with your tested application using CDP or via legacy script injection, then you should check your tested application type (WPF-based or not) and how it was started according to the information provided in the referenced help article.