03 11 2026 Meeting - vanderbilt-redcap/redcap_cypress GitHub Wiki

🚀 March '26 Automated Testing Subcommittee

🧠 Part 1: Structured Discussion (First Half)

Support for External Module fixtures (domain-related test data) and files (assets):

All files, by default, are pulled in through /cypress/fixtures/ folder.

https://github.com/vanderbilt-redcap/rctf/blob/main/commands/data_import.js#L12-L17

Thanks to Mark McEver - RCTF already has support for relative file paths. Example of how to implement here: https://github.com/vanderbilt-redcap/external-module-framework-docs/blob/main/example_modules/module-development-examples_v1.0/automated-tests/file-settings.feature#L51

How do we standardize setup and reduce setup complexity for EMs?

Keeping all files related to External Module within the EM repository
Increasing flexibility of base redcap_cypress repository

For example ... if we don't want to manually adjust Cypress to find step definitions within an External Module, I was hoping to use this configuration:

https://github.com/vanderbilt-redcap/redcap_cypress/pull/262/changes

    "stepDefinitions": [
      "cypress/support/step_definitions/*",
      "../redcap_source/modules/**/automated-tests/step_definitions/*.js"
    ]

I kept this is as a draft PR because I've seen some problems with this approach even though it is recommended by Cypress officially.
Cannot explain why, but I've seen it cause some errors on Cypress.
Loaded this configuration on a peer's machine and it was giving this error:

I've not seen this occur on my machine and I wonder if it might be related to Node version.