bitovi/funcunit

Set up SauceLabs for browser testing

Open

#207 opened on May 11, 2017

View on GitHub
 (3 comments) (0 reactions) (0 assignees)JavaScript (575 stars) (395 forks)batch import
developer relationshelp wanted

Description

We ran into an issue where Funcunit was throwing an error on Chrome 58 on Windows 10: https://github.com/canjs/canjs/issues/3235. We should set up SauceLabs testing for funcunit so we can catch these issues earlier.

Setting up SauceLabs is relatively easy using the test-saucelabs package like we are using in canjs here: https://github.com/canjs/canjs/blob/master/test/test-sauce-labs.js.

Contributor guide

Tech stack
javascript
Domain
testing
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
JavaScriptbasic testing knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Set up SauceLabs for funcunit following the test saucelabs package as used in canjs (https://github.com/canjs/canjs/blob/master/test/test sauce labs.js). The issue references a previous bug on Chrome 58 and aims to catch similar issues earlier. Check the current compatiblity of funcunit with SauceLabs and adapt the configuration accordingly.