Testing Approach as a Windows Insider -Part 1
As #WindowsInsider build 18323 rolls out and #bugbash is underway the way that you install, test, experiment, troubleshoot and use the insider build is an important step in the whole Windows insider process.
Your testing options are as open as the sky but you should develop a personal strategy that you can use over the build cycle that you can use as a reference approach. Some basic essentials that you should think about while testing are:
1) Casual testing or more then casual
2) Fast or slow Ring
3) Bare metal or Upgrade testing or both
4) x86 or x64 or both
5) Virtual or physical testing or a mix
6) lots more!
As this build cycle comes close to being completed there are lots of streams that are being merged together. As an insider, a strong approach you can take is to review the build notes on every release - A good overall link to use is the flight-hub which will get you a detailed picture of the new builds found within this flight and the full specs on what the build contains.
Whether you are a casual or more then casual tester you need to have the flight hub or build release notes as the first thing you look at PRIOR to you clicking and accepting the download. This explains in detail all the new features, changes and known issues in this build - this should be a cornerstone or where you want to start your testing!
My recommendation is that if you are going to be a casual tester you should be in the slow ring - The slow ring is less susceptible to issues as is the fast ring - The fast ring sees a new build once a week. If you are not committed to reading up on, installing and possibly troubleshooting this once a week this is why I suggest the slow ring. No harm or stigma associated with the slow ring, its really based on how casual or intense you can commit to being a #WindowsInsider Jumping from slow to fast and back to slow is not a great approach and once you commit to a ring - on one of your testing platforms - stick to it! - There is no reason you can't have multiple test platforms however!
If you are committing to the fast ring, or skip ahead ring for that matter please ensure you are flexible and willing to wipe out and recover this device in the event that something goes sideways or you cannot recover from some technical oversight in the new build. The insider team tries to NOT brick your computer but you need to be open to the fact that this can and does happen from time to time. When it does, my best advice is to reachout to the tech community or ms answers forums for insight or experience on exactly what can be done to get you back on track. Recovering the device from settings or at worst cleaning the drive with DISKPART and laying down the newest working ISO might not be attractive but has ALWAYS worked for me.
In a nutshell Casual Tester --> Slow ring
More then casual tester --> Commit to the fast ring
Look for Part 2 on Testing with talking about Baremetal vs upgrade and x86 vs x64
Happy testing and follow me @Murmanz