Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multi Step WebTests #26050

Closed
karthikdevarakonda opened this issue Mar 1, 2019 — with docs.microsoft.com · 2 comments

Comments

Projects
None yet
4 participants
Copy link

commented Mar 1, 2019 — with docs.microsoft.com

Hi,

With the deprecation of multistep webtests, Can you please provide an alternative for the same to continue with the availability tests.

Thank you
D Karthik


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

@morgangrobin

This comment has been minimized.

Copy link
Contributor

commented Mar 1, 2019

Hi @karthikdevarakonda, thanks for the question!

I am a PM on Azure Monitor, currently focused on the availability monitoring space. This is a problem that I'm currently looking at and trying to solve.

Current state is: As of right now, we have no plans to drop support for Visual Studio multi-step tests, and (although this is not a guarantee), we do not intend to drop support for them without a 1 year lead time, a sufficient replacement, and migration guidance. Visual Studio 2019 will still have the ability to write multi-step tests, and the support lifecycle for a Visual Studio product is 5 years. My recommendation is to continue using Visual Studio multi-step web tests.

That being said, eventually support for these tests will be dropped. We understand that no one wants to invest in a technology that will eventually be deprecated , however we do not yet have a sufficient replacement in this space.

There is a workaround for which support will not be deprecated - and that is to run your own web tests in any language for which we have an SDK, run them on your own server or on Azure functions/containers/VMs, and send the results to your Application Insights resource using the TrackAvailability() API. This is a more DIY approach, as you are then responsible for ensuring your test runs at regular intervals and sending the test results to App Insights. This approach also has limitations with how much data is displayed in the portal, but we are improving the amount of information that is displayed in the next few months.

@BhargaviAnnadevara-MSFT

This comment has been minimized.

Copy link
Contributor

commented Mar 2, 2019

@karthikdevarakonda Hope @morgangrobin's response answers your question!

We are now going to close this thread as resolved, but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.