DevOps is getting significant attention in the industry. Many organizations don’t understand what DevOps is, how to adopt DevOps practices effectively within the organization, and are not aware of what DevOps tools to use. Toronto Enterprise DevOps User Group is focused on applying DevOps practices in the enterprise environment. This group is for people in the Greater Toronto Area who are interested in continuous deployment/integration, release management, infrastructure as code, change/configuration management, load testing & auto-scale, performance/availability monitoring, capacity management, automated testing, automated environment provisioning/de-provisioning, self service environments, automated recovery (rollback & roll-Forward), and many more of constantly evolving DevOps practices. Every level of experience is welcome, all we ask is that you come with an open mind and are excited to share your knowledge.
Great video and very helpful, thanks PS you might want to blur out the email addresses you've shown in your Kanban board? can do it in the youtube editor without taking the video down. Cheers
Great video, unfortunately I kind of blocked on running the tests since its for a mobile app (iOS-Android). This feature is more helpful for web apps or desktop apps.
How do you gather metrics of pass/fail test cases? We would like to measure first time quality but it appears after a test initially failed and then passes, you only see the final result in history.
@27.56 Say if I have 2 more Static suites eg. Sprint 3, 4 and 5 besides the one (Sprint 2) you have. And I need to move the stories that are under Sprint 4 to Sprint 2 suite, how do I do that in bulk?
Thankyou Dave. How did you get the Test Case to show up on the sprint cards? I can add test cases to bugs and tasks but when I look at the sprint, I don't see any of them showing that they have tests. I looked in add fields and it has things like State etc. but not Test Case.
Is there a way within DevOps 2020 to combine a specific set of test plans and their suite into 1 giant test plan? If one can do this when combining is there a way to not link those items together, and will a new unique ID will be included when doing this? Trying to figure out a way to gather a specific set of defined test plans (their suites and cases) into their own separate test plan without affecting the orginal's test outcomes and ensuring they are unlinked.
This started like a joke. Too much background noise and distraction by someone shouting Dave! Finally, i learnt something valuable. Help improve the quality next time.
I am trying to use the backup environment task and getting 403 forbidden. I use an app registration configured as app user with System Admin permissions in the target Power Platform environment. Any ideas?
Thank you so much for the amazing Video. But when I am executing some test cases in one Suite in Test Plan and moving it to another Suite already executed test cases are changing the status to Active is there any solution to remain status same if I move the test cases to another Suite.
I need a litle help. When you take the work items by suite into the plan and then you see that one is not correct can you delet it without causing the delet from the work item?
If you are interested in how I use Azure Test Plans I wrote 4 short articles on Medium you might be interested in: daveklloyd.medium.com/azure-test-plans-test-cases-39aa1fb1e9b7?source=your_stories_page------------------------------------- daveklloyd.medium.com/azure-test-plans-test-plans-212fbaaa68e3?source=your_stories_page------------------------------------- medium.com/objectsharp/azure-test-plans-test-execution-e8a20c809e4e?source=your_stories_page------------------------------------- medium.com/objectsharp/exploratory-testing-6f247adb62c0?source=your_stories_page-------------------------------------
Is there a way to lock a test plan? For example I created a test plan with query based suite (all test with prio 1). The test plan was completely executed and now I created new test plan for current iteration. with new requirements coming in I also added some additional prio 1 test to azure. What I see is that even the old test plan that was already executed starts to pull these new tests with prio 1 into its query based suite. Is there a way to lock a this already completed old test plan?
Is it possible to assign multiple testers for execution to a test case? I know I can do it on the test suite level, but I cannot do it for a test case.
Thanks Dave. For tests how do you know when they are ready to perform if they are linked to a PBI? When the PBIs or BUGs state is updated do they get reflected into the test?
If you are using Azure Pipelines you can tie in workitems to the release to let people know what has been deployed. for example the Release can show what Stories or Bugs have been included in a particular release.
Thanks Dave for the wonderful video! Can you please whether we can implement automation in Azure Devops? Or can we just execute automation via Azure Pipelines?
Automated tests should be executed via Azure Pipelines that just makes sense. You can hook automated tests up to a test plan and execute them as you execute the test plan. I have not done this in years and I'm not sure how good the experience would be anymore. Azure Pipelines if the way to go.
Does anyone know how to make a testing process where the first step is creating test plan, test suite, test case which should be attached to work item or the same test case is used for more different work items?
You can just create the test plan then used test suites to add the test cases, either static (like a folder within the test plan) a query or requirement. Only requirement assumes the test case is attached to another work item. The other two suite types allow you to just add test cases to your plan regardless of the requirements they are attached to. Does that answer your question?
Do you have a solution for when Cloud Flow is used in canvas app and upon solution import, the connection is broken between the flow and the canvas app and apparent needs to be manually reconnected?
Thank you Dave for the demo! What happens if you create a requirements based test plan based on Iteration or Area path which is from the Sprint but that user story gets moved to another sprint? Assuming the test automatically gets moved to new test plan (providing another one gets created)? This is my hesitation with dynamic test suites as they can disappear without knowing and then move to another test plan. Just curious if you have thoughts around this or I am approaching this issue with too much complexity.
Nothing should disappear. how an agile team handles stories that do not get finished in a sprint should take into account what happens to the test plan. The test cases will still be attached to the original Story. If a new story is created you can just attach the test cases here also. When this story is pulled into the test plan for the new sprint they will come with it.
I am not totally sure what you are asking. If you mean is it better to use static test suites or requirement based. My preference is requirement based but you do whatever works for you.