Skip to content

Create enabling-and-disabling-modules-in-control-center.feature - #24

Open
mmcev106 wants to merge 1 commit into
mainfrom
mmcev106-patch-1
Open

Create enabling-and-disabling-modules-in-control-center.feature#24
mmcev106 wants to merge 1 commit into
mainfrom
mmcev106-patch-1

Conversation

@mmcev106

Copy link
Copy Markdown
Contributor

Pre-flight Checklist

  • Have all lines in this PR been reviewed & optimized by a human with appropriate coding skills?
  • Are all the features in this PR tested by a human?
  • Have other features this PR touches also been tested by a human?
  • Has the code been formatted for consistency and readability?
  • Did you also update related documentation and tooling, such as .readme or tests?

Adding the new cypress test we wrote together on our weekly call

@ChemiKyle
ChemiKyle requested review from Ehaic, moorejr5 and tmwil August 12, 2026 19:08
@ChemiKyle

Copy link
Copy Markdown
Contributor

Everyone added as a reviewer, please set up https://github.com/vanderbilt-redcap/redcap_cypress_docker and run this feature before approving. If anything is ambiguous or difficult during setup, please complain! You're also assessing the accessibility of writing and running these tests before you lose your valuable ignorance.

@mmcev106

Copy link
Copy Markdown
Contributor Author

Valuable ignorance indeed! If you get stuck on anything, please ask before spinning your wheels so I that can streamline that step for the next person 😊.

@moorejr5 moorejr5 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When I was trying to run the run.sh file, I got the following errors:
/usr/bin/env: ‘bash\r’: No such file or directory
/usr/bin/env: use -[v]S to pass options in shebang lines

This is because I am in Windows, and running the commands in WSL. Because of Windows being a stupid dumb-dumb, it doesn't know how to do newlines.

To fix it, I had to run the following command to get Git to stop letting Windows be an idiot:
git config --global core.autocrlf false

Then to reset the Git repo, these commands:
git fetch origin
git reset --hard origin/main

Outside of that, the documentation was very helpful to get the environment set up. My own ignorance of using Cypress itself made creating the new feature file a little odd (I couldn't figure out how to do it within cypress itself with our setup). However, I'm not sure that hand holding that part is 100% necessary for our docs when Cypress' own official information exists.

@mmcev106

Copy link
Copy Markdown
Contributor Author

@moorejr5, I really appreciate the feedback! Were you using Git Bash? I believe that's what the docs say to use, but let me know if that's not clear at any point in the docs. If you weren't using Git Bash, what console were you using? I'm surprised it worked at all if it was CMD, PowerShell, or WSL.

@moorejr5

Copy link
Copy Markdown
Contributor

@moorejr5, I really appreciate the feedback! Were you using Git Bash? I believe that's what the docs say to use, but let me know if that's not clear at any point in the docs. If you weren't using Git Bash, what console were you using? I'm surprised it worked at all if it was CMD, PowerShell, or WSL.

I was just using WSL. I run everything through that. The docs mentioned Git Bash but didn't see any reason WSL's command line wouldn't work like it does for all our other scripts.

@mmcev106

Copy link
Copy Markdown
Contributor Author

@moorejr5, just FYI, you may have have performance or path mismatch issues in WSL for certain subsets of functionality. That's very interesting to know it worked at all though!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants