Create RT2 testing workflow for local machines

[alainna]

Why?

When meeting w/ Chad to triage RT2’s Ruby environment (re: dependabot branches), he suggested that we implement a more robust testing system for RT2.

This new workflow should allow programmers to test RT2 changes locally, with dummy XWALK output files, to “cut out the middle man” of the Elements UI process of impersonating & depositing (sometimes onerous in its length).

What?

• Replicate Subi staging Ruby environment locally
• Create a dummy XWALK output file
  • This should essentially have all the inputs a publication could have, even the strictly optional ones.
  • Different dummy input files may be reasonable for (e.g.) different publication types.
• Create a wrapper program to feed RT2 dummy data
• Create a wrapper program to capture RT2’s output and display/print it locally

---

Steps

• Replicate staging Ruby environment

• Create dummy xwalk file(s)

• Create a wrapper program to pass RT2 the dummy local data

• Create a wrapper program to capture & display RT2 output

---

Earlier: https://trello.com/c/ukvzzhdW