Woody Leonhard's no-bull news, tips and help for Windows, Office and more… Please disable your ad blocker – our (polite!) ads help keep AskWoody going!
Home icon Home icon Home icon Email icon RSS icon
  • How to be a Beta Tester

    Posted on geekdom Comment on the AskWoody Lounge

    Home Forums AskWoody support Windows How to be a Beta Tester

    Topic Resolution: Not a Question

    This topic contains 0 replies, has 1 voice, and was last updated by  geekdom 2 months ago.

    • Author
      Posts
    • #223895 Reply

      geekdom
      AskWoody Lounger

      This short instructional sheet provides basic information on how to be a beta tester. It is not designed to be the catch-all, do-all for beta testing, but will provide some basic preliminary steps. You may choose to do things differently, and by all means, make use of all your options when testing to insure you have the best information available.

      1.    Decide what you are going to test and how you are going to test.

      2.    The following instructions are for system updates, but have application for any testing: https://www.askwoody.com/forums/topic/things-to-do-before-making-system-updates/

      For sure, backup up your system. Make a full backup and have a boot disk at hand. Sometimes beta testing goes really wrong, and if you decide to be ahead of the curve, you have a plan when everything fails.

      3.    Test one step at a time. Let’s say you need to provide system updates and test brand-new-to-you software. Do one thing at a time. Not altogether. If one or the other fails, you won’t know which did what.

      4.    Think of the item being tested as a black box. You provide input in the form of tasks or instructions and you get output in the form of results. You don’t really know what’s in the black box or how it functions.

      5.    Run your beta test based on vendor-provided information. You might consider reading reports from other reliable sources. You are beta testing, remember. Normally, beta testing goes ahead of the curve and you are on your own.

      6.    At the start of your report, include information regarding your computer system, operating system, firewalls, anti-virus software, and any other pertinent information.

      7.    Log your results objectively. Note what fails and how with complete error messages. Note the procedures used and your steps. “This program stinks” is not an objective view and helps no one who is attempting to get things to run correctly. “It didn’t work” is also not helpful.

      8.    Make sure your report is comprehensible. Save for a later date. You may have to refer to it often especially in light of later testing.

      Group G{ot backup} Win7 · x64 · SP1 · i3-3220 · TestBeta
      • This topic was modified 2 months ago by  geekdom.
      2 users thanked author for this post.

    Please follow the -Lounge Rules- no personal attacks, no swearing, and politics/religion are relegated to the Rants forum.

    Reply To: How to be a Beta Tester

    You can use BBCodes to format your content.
    Your account can't use Advanced BBCodes, they will be stripped before saving.

    Your information:


    Comments are closed.