Can we make recording test mode switching easier
See original GitHub issueEnvironment variable requires a restart Changing the source is cumbersome and leads to people checking in the test mode.
What about allowing a testmode.txt
file in the test project directory that would control test mode and not require VS restart?
Issue Analytics
- State:
- Created 3 years ago
- Comments:20 (20 by maintainers)
Top Results From Across the Web
Changing screen recording to try mode after test mode?
If you've already perfected your test mode, it is possible to duplicate it and treat it as a try mode, but you'll have...
Read more >How to turn a screen recording into test slides - YouTube
In this tutorial we 'll show you how to use a screen recording as a series of step by step test slides in...
Read more >Good approach to switch database for Test mode / Sand ...
I would not consider using a "test mode switch " a good idea as it makes far to easy to inadvertantly mess things...
Read more >Two Tips to Get the Most Out of Test Mode
There is a better way! Tip 1 - You can actually run a Flow or Web Service listener process in test mode, you...
Read more >What Is test mode and how do I turn It off and on?
Drag the toggle to Live. The interface will confirm that the Test Mode settings have been successfully applied and the account is now...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
We often want to run our tests live from our dev workstations, and not necessarily re-record. I might be debugging or something. Please don’t make me do a bunch of filesystem tasks. I just want a simple, local, temporary way to switch my test mode.
Likely wouldn’t be enough. VS starts a lot of subprocesses - even for language and build services - and all those would have to be restarted, and restarting some of those would likely crash VS. Much the same for VSCode. Just best to avoid environment variables.