Difference between revisions of "BETA"
Jump to navigation
Jump to search
m (→Guidelines) |
m |
||
| (15 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
= | =Beta Testing Group= | ||
NCF Beta Testing Group consists of members willing to assist | 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. | # 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. | # 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. | #* 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. | ||
| Line 10: | Line 10: | ||
# 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 | # 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 | # A member may request to join the Beta Testing Group by emailing [mailto:beta@ncf.ca beta@ncf.ca]. | ||
# Most communication with Beta testers will be by email. | |||
# 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 | # 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. | ||
#** '''Schedule of Testing Activities''' | #** '''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''' | #* '''Feedback''' Survey for testers. | ||
#** '''Escape Plan''' Describe clearly what testers should do if things go wrong ( | #* '''Report''' Provide a summary to testers on what was discovered or determined during testing. | ||
#* '''Feedback''' | # 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 | |||
=Service Disruptions during Testing= | =Service Disruptions during Testing= | ||
# | # 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. | ||
# | # 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. | ||
# | # 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
- 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 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.
- 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
- 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.
- Members can abandon a Test Case if service disruptions occur and contact the Help Desk for help troubleshooting their service issue.
Process
- A member may request to join the Beta Testing Group by emailing beta@ncf.ca.
- Most communication with Beta testers will be by email.
- Beta Testers who pass Test Case suitability screening will be sent an invitation to join a Test Case.
- 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.
- 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
- 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.
- 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.
- Contact the Help Desk by emailing support@ncf.ca or calling 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
- Hardware - modems, routers and accessories
- Network
- Products and Services