Thank you for the explanation! Can you please share the best practice to maintain the test plan/suite structure if the process is CMMI and we test the build in multiple cycles until all defects are resolved.
Hello @Ravikanth - In this video, You have explained - How to import Regression test suite from Module, but there is catch here because it is not always necessary to include all test cases from selected module. It would be great if you explain If anyone wants to import regression test suite by selecting modules as well as Test cases within it.
Regarding regression tests: test cases will change over time, because new releases might change existing features. But if you make a change in the test case in the master regression suite, then all the previous releases will reference the new version (because importing a suite simply puts a "reference" on the original test case). This is not an optimal approach for traceability (e.g. I will not be able to check what did I test 3 releases ago). As Azure Test Plans does not support versioning test cases, at the moment I have no better idea than the "well-known" copying/archiving mechanism. I create a third folder called "archived regression tests". Any time I make a change in the regression suite, I create a new test case and "archive" the original one. I'd be curious about how you would solve this.
The only way is to follow your approach. However, once the application is mature enough to identify regression suite, the changes should not be major. If you find major change, then you need to identify a new regression test case and add it to suite, so that you can import that new test case to new release.
Hello, Ravi Kanth for your useful videos. I haven't found such informative videos on azure DevOps till now. Recently, I am looking for delivery plan dependencies. But can't find a solution in any video. I would love it if you can make a video of task dependency through the delivery plan.
Please while watching lesson 2, on test plans I could not see new test plan menu when I click on test plans. I checked on org and protect settings I didn't see. I was unable to continue watching that video as I like practicing while watching. Please can you direct me? Thank you.
Hi Ravikanth, thank you for the tutorial. I have a small doubt in defining the automation status of test case. When can we update the Test Case automation status as Planned, Not Automated and Automated. This this what my thought on this. Correct me if I am missing something. Planned: ? Not Automated : Not written the automation script Automated : Written the automation script
Hi In our project we do every 2 weeks release and we work on agile process question 1 :what do you suggest for creating test plan ,do i need to create test plan for every sprint or have to go with release test plan ? question 2 : For doing the regression testing for every sprint how to pull the test cases, can i create the tags for specific test cases and add to regression test suite? Question 3: In sprint board there will be some bugs tickets created which found in the regression so i need to create a separate requirement based suite ? could you please answer these ,Thank you.
Thanks alot for the nice lecture. I had a question, what if I create 2 test suites and both have some test case in common. example I create a query based suite with test case priority 2 and a another query based suite with tag "abc". in this case test cases with priority 2 and tag "abc" will exist in both suites. could you please guide how can I identify duplicate test cases in my test plan?
@@RavikanthReddy this is correct, two different test case instances will be created and then when both instances will be separately executed we will have 2 separate results for the same test case. Problem here is that it would be a wastage of test effort, is there a way to eliminate duplication? or a way to identify duplication of same test case in a test plan?
@@KamranKhan-hv5ti it's not wastage. This is how you have to call same test case whenever required for any release instead of writing new test casem. This way we can save time.
Can you please create a video with detailed explanation about LINK TYPES? In which cases to choose given types: child, parent, duplicate, related, predecessor, test case, tested by etc…. I can not find a short explanation on the internet, unfortunately. Or anyone can send a link with explanation of every type of link? Thank you
Tricentis Tosca automation tool Latest verison Tosca 16.0 is releasing on 8th Dec'2022. I will start posting RUclips videos on this latest version from next week. Please stay Tune to my Channel..!!
Hello Ravik!! You are a Genius!!💯 Thank you for created this material and shared!!
Thanks a lot! Please do subscribe to my channel
Thanks Ravik for share the lesson. It's helpful for community. Please keep going.
Glad you liked them. Please subscribe to my channel
Nice explanation Ravi. Very useful for testers👏
Thank you and please subscribe to my channel 🙏
Thank you for the explanation! Can you please share the best practice to maintain the test plan/suite structure if the process is CMMI and we test the build in multiple cycles until all defects are resolved.
Email me to ravikaanthe@outlook.com
Thank you for this! Really helpful
Glad it was helpful!
Hello @Ravikanth - In this video, You have explained - How to import Regression test suite from Module, but there is catch here because it is not always necessary to include all test cases from selected module.
It would be great if you explain If anyone wants to import regression test suite by selecting modules as well as Test cases within it.
Regarding regression tests: test cases will change over time, because new releases might change existing features.
But if you make a change in the test case in the master regression suite, then all the previous releases will reference the new version (because importing a suite simply puts a "reference" on the original test case). This is not an optimal approach for traceability (e.g. I will not be able to check what did I test 3 releases ago).
As Azure Test Plans does not support versioning test cases, at the moment I have no better idea than the "well-known" copying/archiving mechanism. I create a third folder called "archived regression tests". Any time I make a change in the regression suite, I create a new test case and "archive" the original one.
I'd be curious about how you would solve this.
The only way is to follow your approach. However, once the application is mature enough to identify regression suite, the changes should not be major. If you find major change, then you need to identify a new regression test case and add it to suite, so that you can import that new test case to new release.
Hello, Ravi Kanth for your useful videos. I haven't found such informative videos on azure DevOps till now. Recently, I am looking for delivery plan dependencies. But can't find a solution in any video. I would love it if you can make a video of task dependency through the delivery plan.
Hello Ravi,
Thank you for the informative guide. How do I clear results in test suits that were previously sent out?
Nice explanation, Please provide some unique real time scenarios..........
Thank you and Sure upload more videos with real-time examples
Please while watching lesson 2, on test plans I could not see new test plan menu when I click on test plans. I checked on org and protect settings I didn't see. I was unable to continue watching that video as I like practicing while watching. Please can you direct me?
Thank you.
Thank you! Very helped )
Please do subscribe to my channel
Hi Ravikanth, thank you for the tutorial. I have a small doubt in defining the automation status of test case.
When can we update the Test Case automation status as Planned, Not Automated and Automated.
This this what my thought on this.
Correct me if I am missing something.
Planned: ?
Not Automated : Not written the automation script
Automated : Written the automation script
Planned means, you identified all test cases for automation and you planned to automate.
Please subscribe to my channel
Hi
In our project we do every 2 weeks release and we work on agile process
question 1 :what do you suggest for creating test plan ,do i need to create test plan for every sprint or have to go with release test plan ?
question 2 : For doing the regression testing for every sprint how to pull the test cases, can i create the tags for specific test cases and add to regression test suite?
Question 3: In sprint board there will be some bugs tickets created which found in the regression so i need to create a separate requirement based suite ?
could you please answer these ,Thank you.
Thanks alot for the nice lecture. I had a question, what if I create 2 test suites and both have some test case in common. example I create a query based suite with test case priority 2 and a another query based suite with tag "abc". in this case test cases with priority 2 and tag "abc" will exist in both suites. could you please guide how can I identify duplicate test cases in my test plan?
Eventhog, you pull same test case in both suites, while execution it creates two different instances and you get to different test results Instances
@@RavikanthReddy this is correct, two different test case instances will be created and then when both instances will be separately executed we will have 2 separate results for the same test case.
Problem here is that it would be a wastage of test effort, is there a way to eliminate duplication? or a way to identify duplication of same test case in a test plan?
@@KamranKhan-hv5ti it's not wastage. This is how you have to call same test case whenever required for any release instead of writing new test casem. This way we can save time.
Is it possible to link testsuite and Testplans under task ?
yes, we can link test suite or test plan to any work items 'Task' that you create in Azure DevOps.
Can you please create a video with detailed explanation about LINK TYPES? In which cases to choose given types: child, parent, duplicate, related, predecessor, test case, tested by etc….
I can not find a short explanation on the internet, unfortunately.
Or anyone can send a link with explanation of every type of link?
Thank you
Sure Liana. I will try to make a video on link types.
Please subscribe to my channel
Tricentis Tosca automation tool Latest verison Tosca 16.0 is releasing on 8th Dec'2022. I will start posting RUclips videos on this latest version from next week. Please stay Tune to my Channel..!!