IanSmith
New Contributor
Joined 3 years ago
User Profile
User Widgets
Contributions
Location of TestComplete output log messages when running under Azure Dev Ops
Hi, I'm relatively new to TestComplete and am running a TestComplete project from Azure Dev Ops via a pipeline connected to an agent on my local machine running Windows 10 Enterprise, and am trying to find the value of a path (including Project.Path) being set for an Excel read, as the Excel read that follows it fails. (It works fine when run locally). The pipeline is set up to run using TestComplete, and points to a project file, running tests listed and checked as test cases in Execution Plan. The test platform version is 'Installed by Tools Installer'. Visual Studio Test Platform Installer uses 'Latest Stable'. When vstest - testAssemblies runs, Azure Dev Ops logs its own activity but refers the reader to log files when tests fail, as per attachment. Does anyone know where TestComplete logs are written to in this scenario? I would like to see information I've logged using TestComplete's log message but can't seem to find any other log files. Those in TestComplete only hold log.message lines from tests run from within TestComplete itself. Is it the case that log.message is disabled while running in a remote pipeline and that trying to get debug information this way just isn't supported?Execution Plan changes not reflected in Azure Dev Ops pipeline run.
Hi everyone, I have a TestComplete 15 project which I use to test a bespoke Windows application, is bound to an Azure Dev Ops project and uses GIT as source control. If I change the content of my execution plan, it is recognised by GIT as a modified project. Subsequent Commit and Push appear to work successfully. The log doesn't mention the execution plan. The git status on the project changes back to a tick. At this time, in TestComplete, the execution plan remains how I redefined it. (This changes below). When I run a pipeline quoting the project's pjs and test defined as "execution plan", it uses the previous definition of the execution plan, not my changed version. When I restart TestComplete (having shut it down for the pipeline agent), the execution plan reverts to the previous version, losing my changes. My question is: Is there an accepted way of updating the execution plan in TestComplete so that it is recognised by Azure, and is not subject to this regression?