Forum Discussion

Regular Contributor

2 years ago

execution plan enabled difference between local and azure

i have an execution plan that doesn't always have every test item/test case enabled. i came up with the following for loop that (when the plan is running on my local machine) is able to...

AlexKaras
2 years ago
Hi,

I am not Azure guru and might be wrong here, but my understanding is that VS Test Steps component makes it possible to utilize unit tests runner to execute unit tests. And, as per Support, TestComplete Test Adapter is used to provide this runner with a list of tests (that will be executed using unit tests concept). So I think that both these components can be removed if you are going to use Command Prompt task.

Not sure about e-Mail step - it might or might not work depending on how it is configured. For example, it may stop working if it is set to mail published test result (as the result is published by VS Test Step adapter, if I am not mistaken). But if e-Mail sends result that is prepared by TestComplete itself, than I see no reason why it should stop working.

dhundley

Regular Contributor

it's also been my experience with running the testcomplete execution plan from azure that the testcase will run if the testcase checkbox was checked when the commit is made even if the enabled checkbox in the name column is not checked. that seems wonky to me.

dhundley

Regular Contributor

2 years ago

i have never used the parameters feature of testcomplete before. is there perhaps some way of accessing the test item's or test case's parameters inside the event handlers? that might be a solution but how do i access the value of the parameter that i put on on the keyword test from within the event handler?

dhundley
Regular Contributor
2 years ago
ok. i may have found a solution that is so simple it is jaw dropping. I just want to know if it will still be a solution when it has been committed and is running from azure. instead of using parameters i noticed the Description field on the properties page. I can easily put the test "First" in the Description field of the first enabled test case on the execution plan and "Last" in the Description of the last enabled test case

i can then set up my event handlers as shown here and it runs successfully in my little test project running on my workstation IDE

but will it work running from azure? if so, chalk one up for Occam's Razor
- AlexKaras
  Champion Level 3
  2 years ago
  Hi,
  
  If I got your problem right, than the issue is not with TestComplete but with Azure (and other CI runners) built using a concept of atomic and independent test (which is reasonable for unit tests but far not reasonable for end-to-end ones).
  
  Check this description provided by Support: https://community.smartbear.com/t5/TestComplete-Questions/testexecute-pipeline-Azure-DevOps-doesn-t-stop-project-on-item/m-p/237724/highlight/true#M103766
  - dhundley
    Regular Contributor
    2 years ago
    so the last entry in that post was this:
    
    if i'm understanding this correctly then i should replace the adapter step in my pipeline (shown below)
    
    with a simple command prompt task in which i use the testexecute command line arguments to run things (see below). does the command prompt also eliminate the Visual Studio test steps? and if that's true then i suppose i wouldn't even need the Visual Studio test platform installer step. not shown in the image above is an emails step at the end that sends an email with any failed test cases. will that step still work with the command prompt step?