02 08 2023 Meeting

Meeting Minutes

Updates to KANBAN board - https://github.com/aldefouw/redcap_cypress/projects/4

• Columns - Added columns to keep things organized
• Feature Written - Means that that feature author has completed their version of a particular feature.
• In Review - Means that I am currently reviewing and modifying the feature to use "appropriate" step defintions.
• Completed - Means that I am done reviewing the feature and it is completed for the time being. Does not mean it cannot change but it means that my review is completed.
• Current Gaps - One thing that Adam D's review has not done is ensure that all of the Gherkin keywords (Given, When, Then, And) are in sequences that make sense. That will ultimately be one of the last things we do because these features are likely to still change moving forward.

Updates to RCTF

• Added an environment variable called hideXHR - it's a boolean value to deal with AJAX or XML HTTP Requests.
• It is added to your cypress.config.js file
• Example now included in repo: https://github.com/aldefouw/redcap_cypress/blob/v11.1.5/cypress.config.js.example
• When TRUE, hides XHR requests so you have less noise to deal with.
• When FALSE, shows XHR requests to troubleshoot AJAX, for example.
• Thanks to Corey DeBacker who mentioned that the XHR requests made it hard to troubleshoot. Gave me idea for scripting something to hide these requests if desired.

Workflow Notes

• Preferred commit style with tags. Example: aldefouw#75. (aldefouw#Issue ID)
• Test Robustness. Discussions about removing brittle pieces like the PID from step definitions.

Status Updates

• Adam D is working through the features that are in Review
• If your feature is written, Adam D will review them in the order they are appearing in the column.
• For those of you who are working on features, are there any features in "To Do" column I should move to the "In Progress" column?

• Mintoo X. would like a generic method to scroll to a place on screen.
• David P. brought up the question of making selectors work robustly for future versions of REDCap.
• • There is no generic answer to this question that will work for every circumstance. It will depend on the stability of the feature or functionality you are testing. We are working to see if Vanderbilt can give us advanced notice of major changes. Outside of that, the best thing to do is select the objects based upon text if possible so we aren't dependent upon specific names or IDs on object.

• Is anyone blocked on moving forward on their feature? We can talk about that and schedule a meeting to meet to get you unblocked.

Meeting Frequency

• We have the monthly overview meeting (aka this meeting). This is a higher level meeting that addresses the project overall.
• For most of us we do not need more meetings. Most of us need more work time. That said, meetings can be productive in some specific cases.
• Adam D will make biweekly meetings available. It would not be mandatory but it could be a meeting where he can dedicate an hour every two weeks to helping us work through some problems together.