Head blueLogoText.gif NCF HelpWiki
Help | StartPage

Difference between revisions of "BETA"

From Support
Jump to: navigation, search
m (Process)
m (Process)
Line 25: Line 25:
 
#* '''Feedback''' Survey for testers.
 
#* '''Feedback''' Survey for testers.
 
#* '''Report''' Provide a summary to testers on what was discovered or determined during testing.
 
#* '''Report''' Provide a summary to testers on what was discovered or determined during testing.
 +
# The Test Case is closed by returning testers accounts to a normal state including but not limited to the return of testing equipment.
  
 
=Service Disruptions during Testing=
 
=Service Disruptions during Testing=

Revision as of 12:40, 22 June 2018

Description

NCF Beta Testing Group consists of members willing to assist Office Staff in testing proposed changes in a controlled environment before rolling it out to all members. Email beta@ncf.ca to join the Beta Testing Group or if you have any questions.

Guidelines

  1. Participation in the Beta Testing Group is voluntary. Members can opt in and opt out of Beta Testing Group at anytime.
  2. Participation in each Test Case is by invitation.
    • A member may not be invited to participate in a Test Case if they have a pending trouble ticket or service issue that will taint the interpretation of testing results.
  3. Members can opt in or opt of each Test Case they're invited to.
  4. Members will generally participate in one Test Case at a time
  5. NCF will not provide direct monetary compensation for testing (e.g. Compensation for time or expertise)
    • NCF may however pass on incentives for testing hardware and services when available.
  6. Members can abandon testing if service disruptions occur and contact the Help Desk for help troubleshooting their service issue.

Process

  1. A member may request to join the Beta Testing Group by emailing beta@ncf.ca.
  2. Most communication with Beta testers will be by email.
  3. Beta Testers who pass Test Case suitability screening will be sent an invitation to join a Test Case.
  4. The Test Case invitation will include a Test Case Plan to members with the following details:
    • Opt In Period: adequate notice to opt into a Test Case.
    • Goals: defining what is being tested and why.
    • Requirements Clear directions on what's need from Beta Testers during the Testing period.
      • Schedule of Testing Activities
      • Test Constraints Specify if testers are allow to Tinker with test elements and if so when. E.g. for the first 24 hours please make no changes to the modem so we can measure line performance.
      • Escape Plan Describe clearly what can go wrong during testings and what testers should do if things seem to go wrong (before contacting Help Desk).
    • Feedback Survey for testers.
    • Report Provide a summary to testers on what was discovered or determined during testing.
  5. The Test Case is closed by returning testers accounts to a normal state including but not limited to the return of testing equipment.

Service Disruptions during Testing

  1. Answer simple Beta testing questions and update member specific tickets
  2. Troubleshoot any service issues as normal and track normally. E.g. DSL No Sync issues that come up will be ticketed and tracked as a DSL No Sync issue.
  3. Refer any specific Beta testing issues and concerns that you cannot address to the Service Operations Manager or Service Development Manager (depending on who has been running a particular Test Case)

Test Areas

  1. Hardware - modems, routers and accessories
  2. Network
  3. Products and Services