What is our primary use case?
We are using
Microsoft Visual Studio for automation testing, specifically using C# Selenium.
Visual Studio Test Case Management, which is embedded in Azure DevOps itself, is part of our process. We have a test plan in Azure DevOps cloud. I have worked in TFS when it was there, and I helped my customer migrate test cases from TFS to Azure DevOps. I created a customized tool using the personal access token to access the APIs from Azure DevOps and built a customized tool to migrate test artifacts from TFS to Azure DevOps.
We are pushing our code repository to Azure GitHub, which is available in the Azure DevOps services. We are pushing that codebase there directly, and Git pull, push, and all these operations are available in Visual Studio. For that purpose, we are using it. In our automation framework, I have established connections by creating and mapping the test cases, mapping those automation test cases, and changing the test case status as automated, which I have done in our automation framework as well.
The integration of Visual Studio with Azure DevOps has improved team collaboration significantly. Earlier, we established connections from Visual Studio to Azure DevOps when TFS was there.
What is most valuable?
The integration of Visual Studio with Azure DevOps has improved team collaboration significantly. In our automation framework, I have established connections by creating and mapping the test cases, mapping those automation test cases, and changing the test case status as automated, which I have done in our automation framework as well.
Regarding the ability of Visual Studio to create feedback loops in our Agile workflow, we are using that in Azure DevOps. We have a retrospective in our auto projects that we are using frequently to get lessons learned, what went well, and what is going wrong, which we are capturing. In Visual Studio, GitHub Copilot is also provided by the organization, so we can provide feedback when our input does not match what we were expecting.
In Visual Studio, my area is in automation testing and QA, so for quality improvement, we are mainly checking the reports and have metrics for the pass rate and fail rate, which we are doing the checking based on that.
What needs improvement?
Visual Studio Test Professional could be improved as earlier we had flexibility in automation testing with TFS, which became a bit difficult moving to Azure DevOps. Additionally, in Visual Studio Code, we have an agent mode for GitHub Copilot, which is very helpful in testing or development phases, while Visual Studio's GitHub Copilot is a bit tricky and sometimes does not provide my desired output.
For future improvements, I would like to see prompt fixing, as currently, if something goes wrong in Visual Studio, the fixing options are not always correct. If that intelligence is embedded, it would be very helpful.
For how long have I used the solution?
I have been working with
Microsoft Visual Studio for more than six to seven years.
What other advice do I have?
I have experience in Selenium with C# and Java mostly, and Robot
Framework as well with Python. I am using GitHub Copilot as well in our automation projects activities. Apart from this, I have experience in UFT also.
We are actually using Azure DevOps, and we are putting our codebase there. We are using the GitHub repository.
I have the experience in pushing the code and then checking in. When we are doing the peer review, I have that experience, but not much experience with Codespaces or GitHub code scanning. I have a little bit of experience in GitHub Actions as well.
I do not have experience with GitHub Advanced Security, but I have DAST and SAST experience, because I have done OWASP testing using C# Selenium.
I am not working with products by OpenText or Tricentis, but we are doing some in-house automation tools, just report analysis, and we are using Azure DevOps OpenAI to check all those reports, such as the automation report and customized automation checkers as well.
For project health assessments, we are not using Visual Studio right now, as everything is in Azure DevOps. The health checkup, metrics, and frequency, along with the requirement traceability matrix, can be mapped there, and even the bugs and different bugs environment are tracked in the dashboards we have created in Azure DevOps itself.
I have provided this review a rating of 9.
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?