I recently deployed Botium v1.7.5 and have been getting "Job failed: Error: Worker finished with error" error. The bot does not detect any user utterance at all and ends the test session with a fail.
I included screenshots of my test case settings, test result and excel sheet containing test cases
I created a test set from manually chatting with my bot, through a feature in Botium, ran it, and it passed.
Related
I am using Azure DevOps pipeline to run my automation test cases.
I am facing an issue that whenever my test run task fails, it doesn't display me the exact error that why the task failed, it just displays "cmd.exe exited with code '1' " for all test lists in the Summary section and the email.
Is there a way I can recieve the information that which test case failed and why in the summary section and email?
I have 5 cmd tasks in my pipeline, each of them has same configuraion, just the test list name is different.
We are no longer able to submit our action to the Alpha and/or Preview channels for testing.
From the Actions Console:
Clicking the Deploy tab
Start New Release
Select 'Alpha' Channel
Clicking Submit
Normally, the page would now refresh and show the draft version being deployed to Alpha.
Instead, we get this error: "Your submission of Version XX was denied"
Note: This error appears immediately, the Action did not go through review and get denied; the submission itself failed. We're not getting any more error info on why the submission failed, and also didn't get any info by email. (Normally, when the Action gets reviewed and there's a problem, we get an email explaining what we should do to fix it)
When trying to deploy the Action from the Google Actions SDK (gactions), a similar error appears:
powershell
PS C:\src\google-action\definitions> gactions push
Pushing files in the project "gluco-check-prod" to Actions Console. This may take a few minutes.
Sending configuration files...
Waiting for server to respond...
Done. Files were pushed to Actions Console, and you can now view your project with this URL:
https://console.actions.google.com/project/gluco-check-prod/overview.
If you want to test your changes, run "gactions deploy preview",
or navigate to the Test section in the Console.
PS C:\src\google-action\definitions> gactions deploy preview
Deploying files in the project "gluco-check-prod" to Actions Console for preview.
This may take a few minutes.
Sending configuration files...
Waiting for server to respond.
It could take up to 1 minute if your cloud function needs to be redeployed.
[ERROR] Server did not return HTTP 200.
{
"error": {
"code": 500,
"message": "Internal error occurred"
}
}
Again, there's no info other than this 500 Internal Server Error.
I have also tried deploying the exact same version that we have currently in Production, and the submission still fails.
Am I overlooking something, or is this an issue on Google's side?
Likewise, we've been unable to submit any releases to preview, alpha, beta or production channels for almost a week.
CLI throws 500 errors, website shows a blank page and all attempted submissions show up minutes later with "submission failed."
Emails to support under the topic Deployment Issues have gone unanswered as well, so there's no way to figure out what's going on or how to fix it.
I am trying to run the Test Compelete Scripts on a virtual machine through Azure DevOps pipeline.
When I run the Azure Devops pipeline release. Execution starts in VM. But when I check the logs I see that the user action in the Test scripts are not performed.
Eg: My application is launched, and next steps when I have to select a radio button execution fails and also in
TE log I can see "User session is disconnected and also I can see that it is not able to identify the object)
You typically get this error when the test is run from a scheduled task with the Run whether user is logged on or not option. The error occurs because in this case the test is run in a non-interactive session and cannot interact with the GUI.
To resolve the problem, do the following:
Modify properties of the scheduled task to use the Run only when the
user is logged on option and specify the user account under which
the task will be run.
Make sure that the specified user is logged into the system when the
task is triggered.
Here is the document you can refer to.
We are using the Publish Test Results task PublishTestResults#2 to publish junit type results in a pipeline in Azure Devops. It has previously worked fine but is now hanging for 10mins (I think this is the default job timeout) and then failing, even though the results have been published. If I try to cancel the job when it starts hanging, the cancel request is ignored and the job continues to hang. Has anyone else experienced similar?
This is the log output whilst the task is hanging
Starting: PublishTestResults
==============================================================================
Task : Publish Test Results
Description : Publish test results to Azure Pipelines
Version : 2.160.0
Author : Microsoft Corporation
Help : https://learn.microsoft.com/azure/devops/pipelines/tasks/test/publish-test-results
==============================================================================
##[warning]An error occurred while sending the request.
Publishing test results to test run '1033544'.
TestResults To Publish 11, Test run id:1033544
Test results publishing 11, remaining: 0. Test run id: 1033544
Async Command Start: Publish test results
We eventually nailed this down to only occurring on agents running as a service, rather than interactively. The problem is that our agents are behind a proxy. We provided the proxy settings as per the instructions but it appears the Publish Test Results task doesn't use that settings, so we had to provide it to the environment that runs the service as well by editing runsvc.sh:
export HTTP_PROXY=http://ourproxy:8080/
export NO_PROXY=localhost,127.0.0.1,localaddress
export HTTPS_PROXY=http://ourproxy:8080/
Publishing test results in AzureDevops Hangs
According to the error message:
[warning]An error occurred while sending the request.
It shows that an error was encountered while sending the request, you could enable the debug log by changing the default variables system.debug to true.
If it worked fine previously and you haven't changed your build definition, then the problem should be caused by your network or Azure devops agent server. You could use private agent to check if it related to the hosted agent.
Besides, for the cancel request is ignored and the job continues to hang, you could set the Build job cancel timeout in minutes in the build options:
So, it won't hang your job all the time.
Hope this helps.
We had the same issue and it really looks like a proxy problem. Since we don't need result files uploaded, the following 'input' helped:
publishRunAttachments: false
I am having an issue with kicking off test cases in Microsoft Test Manager from a script kicked off in Microsoft Release Manager. I can duplicate the issue when just running this command from powershell or command line. Here is the script:
C:\CODE\TCM\TCM.exe run /create /title:"Chads Example Test Case (Run from PowerShell)" /planid:31 /suiteid:2743 /configid:67 /settingsname:"DevWelisRemoteExecution" /testenvironment:"STAR_Regression" /collection:"http://tfssrv64:8080/tfs/DefaultCollection" /teamproject:QA /builddir:"\\tfssrv64\Builds" /include
Running this script returns a test run ID with no errors. I can immediately look in MTM and see the test run has started. It has a state of "pending". It eventually (some 20 minutes later) fails with the error "The test automation associated with the following test case could not be found: [48667]. Run the test case again using a build that contains the binary with the test automation.".
Facts: I can run the same test successfully, with a successful completion, from Microsoft Test Manager. (using the same settings specified in the script) Here are screen shots of the test runs from MTM.
Here is the MTM log of the successful test run.
The log of the successful test run.
Here is the same screen from the failed test run.
Here is the MTM log of the failed test run. Same test, ran from the above script.
The log of the failed test run.
Both test runs are using the same build number. Both test runs use the same test settings and configuration.
Any help would be greatly appreciated.....