Admin UI e2e test status

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

[mxstbr]

Amazing progress here by the way, This is one of the most important issues we have open currently, it’ll massively improve our iteration speed.

Thanks for working on this @joerter @webteckie and @jstockwin, I can’t wait to close this issue!

[jstockwin]

@webteckie Mark me down for some more simple ones i.e. textarea and url for now.

Out of interest, and maybe for future reference, how many checks need to happen on the more complex types? For example, markdown should display with buttons to make text bold and add links etc. Do we check these are there, and working, and then maybe also somehow check the output html is correct, or do we simply just add some text in the field, without many extra checks.