fin-hypergrid/core

Hypergrid and automated testing

Open

#540 opened on Feb 24, 2017

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (148 forks)batch import
Open Discussionsenhancementhelp wanted

Repository metrics

Stars
 (892 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Was wondering if what are the strategies taken by users of hypergrid when it comes to automated testing. Given that dom can't be inspected, its a bit tough to have an e2e harness.

Contributor guide

Research direction
Research testing strategies for canvas based components like Hypergrid, focusing on unit testing of logic and integration testing using headless browsers or custom event simulations.
Tech stack
javascript
Domain
testingfrontend
Issue type
Research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70