My team and I have recently setup testRigor and in doing so created some extraneous test suites. Combing through the dashboard we haven't found an obvious way to remove the extra suites. How can test suites be removed?
Currently, it should be requested on your Slack, the delete test suite functionality is coming up soon.
Related
I have an API test that run within Azure Devops pipeline using TestDataMethod within MSTest. My tests run fine, but problem is all tests reported have the same name, so kind of difficult to figure out which test failed. This works fine in Visual Studio in my local. Is there a way to fix this? I found an old thread for the same issue but has no solution.
Screenshot
As you can see we cannot report the result for each subtest at the root level which also mentioned in the ticket you mentioned. For more information about test result, you could refer to Test analytics, which provides near real-time visibility into your test data for builds and releases. It helps improve the efficiency of your pipeline by identifying repetitive, high impact quality issues.
I am not able to delete orphan test suite (Test suite without any parent Test Plan).
I migrated Test Plan and Test suites using vstssyncmigrator tool. There is issue with Azure DevOps identifying the migrated objects, i.e. Test Plan. When I access test plan from Test Plans options, it firstly shows error but after some time it creates root test suite automatically and the error goes away.
So I want to delete the migrated test suites which are not associated with any Test Plan. Is there any way to achieve this?
I check the microsoft restapi and noticed that we need to have test plan id to delete rest suite.
Any suggestions to clean up this test suite garbage? Any suggestions / help appreciated!
As you said in this case, you can find test suites in the query.You can try to delete these test suites from the query to see if this is work.
Puzzling out how to implement VSTS for testing team.
Regarding the scenario where a manual test is run and a bug is created...
The bug gets prioritized and fixed at some later point.
How does the application indicate to the tester when they can run the test again because the bug has been fixed?
When you run the tests each time it has its own test run ID. That means they will have their own test results even if you run the same test case multiple times (They have different test run IDs).
Generally, once the bug is fixed and the fixed sources are integrated into the next release of the application, then you can run the test again to check if the bug is really fixed or not.
More information about the manual tests please see Run manual tests and FAQs for manual testing
I have a VSO release management definition in which I'm deploying a cloud service and then running some tests. The deployment executes without issues, but then the tests don't run, I recieve the following message in the logs:
Warning: No test is available in My DLL Path. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again.
Now, the strange thing is that this release is triggered by a build, which runs exactly the same set of tests and they all run happily.
I've included a runsettings file specifying the framework version (based on some SO posts I found from a year ago with a similar issue) but its made no difference. Been messing with this for nearly 2 days now with no progress. Any suggestions happily accepted!
Arrrrgh! So it turns out, if I deleted the whole project, created it again and added my tests again, it just works. Gremlins apparently!
Admins, if this needs to be deleted, go ahead
I recently set up a CI server in TeamCity and now want to take it to the next step, continuous deployment. Basically, we host a suite of restful services and about 3 web applications for each one of our customers. All customers get 3 environments QA, UAT and Prod. We want to be able to automatically deploy our builds once our tests pass. I'm not looking for custom scripting options to do this. I've seen plenty of those of SO. What we're looking for is a solutions like UDeploy but at a lower price point. Is anyone aware of alternatives to UDeploy? Or other Continuous Deployment plugins that work with TeamCity?
Thanks,
I agree with #Niklas Ringdahl -- I think you're thinking about it wrong.
You can deploy directly from TeamCity using MS WebDeploy.
See Troy Hunt's excellent blog series about this:
Part 1: Config transforms
Part 2: MS Build and deployable packages
Part 3: Publishing with WebDeploy
Part 4: Continuous builds with TeamCity
Part 5: WebDeploy with TeamCity
If this is .net you should look at Octopus, it now works nicely with TeamCity.
http://www.octopusdeploy.com/
http://www.paulstovell.com/octopus/octopus-octopack-and-teamcity
I don't know if there's any part of this I don't understand, but I would use TeamCity for that also.
If you have a build configuration to manage your tests, you can easily create configurations for deploy, which are triggered by the success of the test configuration. We handle lots of our deploys that way.
Again, sorry if I'm missing something here...
EDIT:
A build configuration in TeamCity can be triggered when another configuration is successfully built:
Build triggering in JetBrains documentation (Look at "Finish Build trigger")
Or you could use one build configuration with many "Build steps":
Build steps in JetBrains documentation
Each step is run in order, and only if the previous step is successful.
Another alternative: RedGate has recently updated pricing on their Deployment manager tool: http://www.red-gate.com/delivery/deployment-manager/
If you have 5 projects or less, the tool appears to be free.
I'm familiar with Nolio ASAP but have no knowledge about its pricing:
http://www.noliosoft.com/product/nolio-automation-center
As a developer for the product, I'll add BuildMaster to the list of options here. Basically, you can run a basic tutorial to get started deploying from TeamCity (http://inedo.com/buildmaster/extensions/teamcity), then customize your deployment plans to any further environments as needed.