keystonejs/keystone-classic

Admin UI e2e test status

Open

#2291 opened on Feb 15, 2016

View on GitHub
 (14 comments) (0 reactions) (0 assignees)JavaScript (14,656 stars) (2,288 forks)batch import
help wantedtesting

Description

This issue covers the current status of the ui/ux/functional e2e tests coverage. Need lots of help here for anyone that's interested! We are using nightwatch to handle e2e testing. All Admin UI e2e tests are under test/e2e/adminUI These are broken into groups and group related tests within those groups. The groups have a sequence number in them to control the order of execution by nightwatch. To run the tests locally use npm run test-e2e. Make sure you have done a successful npm install for the keystone directory first! If you pick a group/test please mention it here to avoid duplication. Ideally we should focus both on positive and negative testing but at this point positive testing is more important to quickly detect regressions!

  • group001Login (ui) -- @webteckie
  • group001Login (ux) -- @webteckie
  • group002Home (ui) -- @webteckie
  • group002Home (ux) -- @webteckie
  • group003List (ui) -- @webteckie
  • group003List (ux) -- @webteckie
  • group004Item (ui) -- @webteckie
  • group004Item (ux) -- @webteckie
  • group005Fields -- some fields may have different states and the tests should cover all states (e.g., a boolean field can be checked or unchecked)
    • azurefile (ui)
    • azurefile (ux)
    • boolean (ui) -- @joerter
      • boolean PO refactoring (ui) -- @jstockwin
    • boolean (ux) -- @joerter
      • boolean PO refactoring (ux) -- @jstockwin
    • cloudinaryimage (ui) -- @jstockwin
    • cloudinaryimage (ux) -- @jstockwin
    • cloudinaryimages (ui) -- @jstockwin
    • cloudinaryimages (ux) -- @jstockwin
    • code (ui) -- @webteckie
    • code (ux) -- @webteckie
    • color (ui) -- @jstockwin
    • color (ux) -- @jstockwin
    • date (ui) -- @jstockwin
    • date (ux) -- @jstockwin
    • datearray (ui) -- @jstockwin
    • datearray (ux) -- @jstockwin
    • datetime (ui) -- @jstockwin
    • datetime (ux) -- @jstockwin
    • email (ui) -- @webteckie
      • email PO refactoring (ui) -- @jstockwin
    • email (ux) -- @webteckie
      • email PO refactoring (ux) -- @jstockwin
    • embedly (ui)
    • embedly (ux)
    • geopoint (ui)
    • geopoint (ux)
    • html (ui) -- @jstockwin
    • html (ux) -- @jstockwin
    • key (ui) -- @jstockwin
    • key (ux) -- @jstockwin
    • localfile (ui) -- @jstockwin
    • localfile (ux) -- @jstockwin
    • localfiles (ui) -- @jstockwin
    • localfiles (ux) -- @jstockwin
    • location (ui) -- @jstockwin
    • location (ux) -- @jstockwin
    • markdown (ui) -- @jstockwin
    • markdown (ux) -- @jstockwin
    • money (ui) -- @jstockwin
    • money (ux) -- @jstockwin
    • name (ui) -- @webteckie
    • name (ux) -- @webteckie
    • number (ui) -- @joerter
      • number PO refactoring (ui) -- @jstockwin
    • number (ux) -- @joerter
      • number PO refactoring (ux) -- @jstockwin
    • numberarray (ui) -- @jstockwin
    • numberarray (ux) -- @jstockwin
    • password (ui) -- @jstockwin
    • password (ux) -- @jstockwin
    • relationship (ui)
    • relationship (ux)
    • s3file (ui)
    • s3file (ux)
    • select (ui) -- @webteckie
    • select (ux) -- @webteckie
    • text (ui) -- @jstockwin
    • text (ux) -- @jstockwin
    • textarea (ui) -- @jstockwin
    • textarea (ux) -- @jstockwin
    • textarray (ui) -- @jstockwin
    • textarray (ux) -- @jstockwin
    • url (ui) -- @jstockwin
    • url (ux) -- @jstockwin
  • group006Relationships (ui)
  • group006Relationships (ux)
  • Cover Lists with noedit:true
  • Cover Lists with nocreate:true
  • Cover Lists with nodelete:true
  • Cover Fields with noedit:true
  • Cover list filtering
  • Cover list columns
  • Cover list download
  • Cover list expand table width
  • Cover negative testing behavior
  • add config/run tests in Chrome browser
  • add config/run tests in IE browser

Contributor guide

Tech stack
javascriptnodejs
Domain
testingfrontend
Issue type
test
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.
1-2 days
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
Basic JavaScriptNightwatch testing frameworkKeystone admin UI basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Examine the test structure under `test/e2e/adminUI` and the nightwatch configuration. Review existing tests (e.g., group001-004) as templates. The remaining tasks include implementing e2e tests for group006Relationships, covering lists with `noedit:true`, `nocreate:true`, `nodelete:true`, and fields with `noedit:true`. Also need to cover list filtering, columns, download, and negative testing. Check comments in the issue for any updates or partial work. Focus on positive testing first.