Head blueLogoText.gif NCF HelpWiki
Help | StartPage

Difference between revisions of "BETA"

From Support
Jump to: navigation, search
(Created page with "=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 me...")
 
m
 
(19 intermediate revisions by 2 users not shown)
Line 1: Line 1:
=Description=
+
=Beta Testing Group=
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.
+
NCF Beta Testing Group consists of members willing to assist NCF Staff in testing proposed changes in a controlled environment before rolling it out to all members. Email [mailto:beta@ncf.ca beta@ncf.ca] to join the Beta Testing Group or if you have any questions.
  
 
=Guidelines=
 
=Guidelines=
# Participation in the '''Beta Testing Group''' is voluntary. Members can opt in and opt out of Beta Testing Group at anytime. Email [http://mailto:beta@ncf.ca beta@ncf.ca]
+
# Participation in the Beta Testing Group is voluntary. Members can opt in and opt out of Beta Testing Group at anytime.
# Participation in each '''Test Case''' is by invitation and requires Beta testers to opt-in.  
+
# Participation in each Test Case is by invitation after a screening process by NCF staff.
#* Members 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.
+
#* 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.
 
# Members can opt in or opt of each Test Case they're invited to.
 
# Members can opt in or opt of each Test Case they're invited to.
# Members will generally participate in one '''Test Case''' at a time
+
# Members will generally participate in one Test Case at a time
 
# NCF will not provide direct monetary compensation for testing (e.g. Compensation for time or expertise)
 
# 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.
 
#* NCF may however pass on incentives for testing hardware and services when available.
# Members can abandon testing if service disruptions occur and contact the Help Desk for help troubleshooting their service issue.
+
# Members can abandon a Test Case if service disruptions occur and contact the [mailto:support@ncf.ca Help Desk] for help troubleshooting their service issue.
  
 
=Process=
 
=Process=
# Beta Testing Group will be managed by the Service Operations Manager and the Service Development Manager
+
# A member may request to join the Beta Testing Group by emailing [mailto:beta@ncf.ca beta@ncf.ca].
# Beta Testing Group will be managed from [https://secure.ncf.ca:2443/helpdesk/Search/Results.html?Query=Queue%20%3D%20%27Beta%27%20AND%20(Status%20%3D%20%27new%27%20OR%20Status%20%3D%20%27open%27%20OR%20Status%20%3D%20%27inprogress%27%20OR%20Status%20%3D%20%27stalled%27) RT] to provide visibility for all staff.
+
# Most communication with Beta testers will be by email.
# Beta Testing will be screened for Test Case suitability on each test case.
+
# Beta Testers who pass Test Case suitability screening will be sent an invitation to join a Test Case.
# Most communication with Beta testers will be by email via RT for visibility to all staff. Calls will be documented as per best practices.
+
# The Test Case invitation will include a Test Case Plan to members with the following details:
# Each Test Case will be ticketed on the member level. Format: '''aa000 Beta Tester 613 <BETA - Test Case 1 - Test Goal> Service Plan'''
+
#* '''Opt In Period''': adequate notice to opt into a Test Case.
#* area code will denote the local area code from which the member has DSL service. Example: '''613''' denotes '''DSL member in Ottawa''', area code '''819''' denotes '''DSL member in Gatineau'''
+
#* '''Testing Period''': Start and end date.
#* area code '''000''' denotes '''non-DSL member'''
+
#* '''Goals''': defining what is being tested.
# Beta Test Group will be provided with clearly defined plan for each Test Case before they opt into it. Test Case Plans will include:
+
#* '''Background''': Explain why tested in being done.
#* '''Adequate notice''': provide a minimum of 1 week to opt into a Test Case
+
#*  '''Requirements''' Clear directions on what's need from Beta Testers during the Testing period.
#* '''Test Case Goal''': define what is being tested and why
+
#** '''Schedule of Testing Activities'''
#*  '''Test Case Requirements''' Clear directions on what's need from them during each stage of the Test Case.
+
#** '''Test Constraints''' Will specify if and when testers are allow to '''Tinker''' with test elements. E.g. for the first 24 hours please make no changes to the modem so we can measure line performance.
#** '''Schedule of Testing Activities''' Soft and hard copies (if necessary)
+
#** '''Escape Plan''' Describe clearly what can go wrong during testings and what testers should do if things seem to go wrong (before contacting [mailto:support@ncf.ca Help Desk]).
#** '''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.
+
#* '''Feedback''' Survey for testers.
#** '''Escape Plan''' Describe clearly what testers should do if things go wrong (including steps to take before contacting Help Desk).
+
#* '''Report''' Provide a summary to testers on what was discovered or determined during testing.
#* '''Feedback''' Solicit tester response on the Test Case and how to improve Beta Testing in General.
+
# The Test Case is closed by returning testers accounts to a normal state including but not limited to the return of testing equipment.
#* '''Report''' Provide a summary to testers on what was discover or determined during testing.
 
  
 
=Service Disruptions during Testing=
 
=Service Disruptions during Testing=
# Answer simple Beta testing questions and update member specific tickets
+
# If you encounter any service disruptions or issues during testing, your first option is to consult the '''Escape Plan''' provided with your Test Case Plan where available.
# 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.
+
# You are allowed to abandone testing at any point to restore your service. For example, during modem testing, you may choose to revert to an old modem to attempt restoring your service.
# 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)
+
# Contact the Help Desk by emailing [mailto:support@ncf.ca support@ncf.ca] or calling [tel:613-721-1773 613-721-1773] x0
 +
# You may resume testing after a service disruption is resolved if you wish to. Your can update your Test Case ticket with any changes, disruptions and issues encountered during testing.
  
 
=Test Areas=
 
=Test Areas=
Line 39: Line 39:
 
# Network
 
# Network
 
# Products and Services
 
# Products and Services
 +
 +
[[Category:Account & Membership]]

Latest revision as of 21:40, 20 July 2018

Beta Testing Group

NCF Beta Testing Group consists of members willing to assist NCF 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 after a screening process by NCF staff.
    • 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 a Test Case 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.
    • Testing Period: Start and end date.
    • Goals: defining what is being tested.
    • Background: Explain why tested in being done.
    • Requirements Clear directions on what's need from Beta Testers during the Testing period.
      • Schedule of Testing Activities
      • Test Constraints Will specify if and when testers are allow to Tinker with test elements. 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. If you encounter any service disruptions or issues during testing, your first option is to consult the Escape Plan provided with your Test Case Plan where available.
  2. You are allowed to abandone testing at any point to restore your service. For example, during modem testing, you may choose to revert to an old modem to attempt restoring your service.
  3. Contact the Help Desk by emailing support@ncf.ca or calling 613-721-1773 x0
  4. You may resume testing after a service disruption is resolved if you wish to. Your can update your Test Case ticket with any changes, disruptions and issues encountered during testing.

Test Areas

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