Skip to content

Latest commit

 

History

History
275 lines (187 loc) · 12.9 KB

TODO-initial.md

File metadata and controls

275 lines (187 loc) · 12.9 KB

This file is an initial list of activities for the MELD testing project. The intent is to tick these off as they cease to become planned tasks, or move them to the GitHub issue list.

All activities

2020-07-29

2020-08-22

  • Join presentation of MELD to BitH project

2020-09-01 and 2020-09-04

  • Progress status of antheia (now back online and publicly accessible)

  • Progress getting seldom back online (hosts MMM video)

2020-10-05

  • Note that BitH testing is not a goal for SSI3, but hope that SSI3 work may inform BitH (e.g. via the report)

2020-10-13

2020-11-04

  • raise simple app in internal SSI3 MELD testing discussion in Oxford.  (see also: minimal selectable-score application, see https://github.com/trompamusic/selectable-score-demo and https://github.com/trompamusic/selectable-score)

  • consider support for tracking React changes?  (Note: any form of testing should go a way toward this.  More generally, problems of moving dependencies.) Consider effect on choice of testing framework.

  • look at changing names of blackList/whiteList in meld core codebase  (dev branch)

    • see issue #1
    • proposed name changes - see issue
    • proposed name changes - see issue
    • [.] discuss new name choices with team
    • [.] apply name changes to codebase
    • [.] see if anything breaks

20290-11-04

  • look into CI for MELD core (see email this date from Kevin)

2020-11-10

  • work with David/Mark to get MELD simple annotation example running

    • Simple Help MELD app is running, with basic score rendering.
    • Add selectable score to "Hello MELD" family
  • think about presenting test framework at mini-MELDfest in spring 2021

  • set up project for MELD testing

    • create project on GitHub
    • pick testing framework; MochaJS? (alt JestJS)
    • Create simple test suite for "Hello MELD"

Activities still TODO

2020-10-13

2020-11-04

  • consider support for tracking React changes?  (Note: any form of testing should go a way toward this.  More generally, problems of moving dependencies.) Consider effect on choice of testing framework.

  • [.] look at changing names of blackList/whiteList in meld core codebase  (dev branch)

    • see issue #1
    • created local "unblacking" branch from git-meld-2.0 branch
    • proposed name changes - see issue
    • [.] discuss new name choices with team
    • [.] apply name changes to codebase
    • [.] see if anything breaks

20290-11-04

  • look into CI for MELD core (see email this date from Kevin)

2020-11-10

  • work with David/Mark to get MELD simple annotation example running

    • Simple Help MELD app is running, with basic score rendering.
    • Add selectable score to "Hello MELD" family
  • think about presenting test framework at mini-MELDfest in spring 2021

  • set up project for MELD testing

    • create project on GitHub
    • experiment with testing frameworks
      • leaning to MochaJS, but for testing node+React server apps, thinking about how the apps should be structured. Will initially test with "Hello MELD"
    • pick testing framework; MochaJS? (alt JestJS)
    • Create simple test suite for "Hello MELD"

Activities to report in period to 2020-12-08

  • new update on RS work to MMM list

  • look at graph traversal code on Lohengrin app

    • Repo for Lohengrin app: Link https://github.com/oerc-music/ForbiddenQuestion , by David Lewis.
    • 2020-10-20: currently stuck finding my way into the app
    • Plan to come back to this when simpler stuff (Hello MELD, selectable score) is nailed
    • Plan to look at next hello meld and score selection with Mark on 2020-12-09
  • set up project for MELD testing

    • create project on GitHub
    • experiment with testing frameworks
      • leaning to MochaJS, but for testing node+React server apps, thinking about how the apps should be structured. Will initially test with "Hello MELD"
    • pick testing framework; MochaJS? (alt JestJS)
    • Create simple test suite for "Hello MELD"
  • work with David/Mark to get MELD simple annotation example running

    • Simple Hello MELD app is running, with basic score rendering.
    • Add selectable score to "Hello MELD" family
  • investigate toolchain for MEI creation. DONE

  • look at changing names of blackList/whiteList in meld core codebase  (dev branch)

    • see issue #1
    • proposed name changes - see issue
    • created local "unblacking" branch from git-meld-2.0 branch
    • [.] discuss new name choices with team
    • [.] apply name changes to codebase
    • [.] see if anything breaks
  • Note that MELD mini-FEST is scheduled for 2021-02-08 (tentative)

Further ACTIONS:

  • MELDfest - think about what to present - "Hello MELD" + testing framework

  • Project timeline outline (MELDfest as milestone - what alternative topics are coming up?) Note timeline for work... thinks we want to explore and things we want to explore. Allow for feedback on write-up. Aim for early feedback on parts of report.

  • 2020-12-09 - Hello MELD discussion. Register MIME type for MEI. (application/mei+xml) (See TEI: https://www.rfc-editor.org/rfc/rfc6129.html)

...

NOTE: warnings about node package versions.

NOTE: By end of project need to articulate an approach (or approaches) to avoiding deprecated library dependencies, as part of SSI3 activity. Also node version dependencies. (see next) Articulate problems of technical debt? Note maintenance load from building on new, fast-moving projects. Isolate dependencies behind API. Use MELD as example...

NOTE: for MELD, raise this early. E.g. raise an issue against meld-client-core. Also suggest possible solutions? (incl CI.)

hello-meld-3 - with linked data

hello-meld-4 - with interactions

@@@ARC app

...

Actions from 2021-06-11 MELD futures meeting:

  • ACTION: GK send link to failing test to Alastair. (hello-meld-2)

  • NOTE to GK for report: in choosing software dependencies, look at recency of updates/active support of package(s) used.