Giter Club home page Giter Club logo

redcap_cypress's People

Contributors

aldefouw avatar andrewpoppe avatar cdebacker avatar krishchant avatar mmpeterson24 avatar mukerji2 avatar rabramley avatar rushi79 avatar tintinn avatar wibeasley avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

redcap_cypress's Issues

Testing External Dependencies (like Mail)

@dr01d3r brought up a good point about external dependencies like mail.

For instance, Manage User tests will likely look at approving an account's email address.

In our next meeting we should discuss how we want to handle this external dependency.

For REDCap, we could do something like this:

Apache or IIS with virtual hosts:

  1. REDCap server (whatever port) mapped to http://redcap.domain.com
  2. MailHog Server (port 1080) mapped to http://mail.domain.com

Question is ... should we?

Krishna Upadhyay

Operating System: Windows Server 2016

Test Environment: IIS10 / PHP7 / MySQL8

Approach for feasibly covering different versions

As we discussed this week with Kyle and others, there are several possible approaches for covering multiple versions of REDCap. It sounds like you'd appreciate the thoughts and feedback from various people.

REDCap versions affect the framework in at least two places:

  1. Installing a specific version by cypress, especially the sql files that seed the data.
  2. The tests themselves. For instance, if a feature was added or modified in 8.2.3, the test should by different (or possibly skipped) when testing 7.4.4.

Cc: @123andy, @mullen2, @pbchase, & @kcmcg

Could/should this be integrated into REDCap Core, the module framework, or specific modules?

I must admit I forgot this library existed... I'm afraid I might do the same again if I don't stumble upon it again for another year or so, and possibly re-implement parts of it as future needs arise. Could/should any existing tests people have written using this framework be incorporated into REDCap Core, the module framework, and/or specific modules so they are automatically available to all REDCap users (and perhaps even automatically run during updates)? I know none of the above are trivial, but I'm curious to hear your thoughts.

Brian Funaro

Operating System: Linux ???

Test Environment: Docker ???

Handling security-related bugs

If a test uncovers a security vulnerability, it shouldn't be available to the public. Maybe we see if vandy would fund a private instance of circle ci (or whatever could be web-scraped/mined but a malicious user looking to exploit a system with phi).

Implement Dynamic User Seeds

Users are configured within the project like this right now:

"users": {
    "admin": {
      "user": "test_admin",
      "pass": "Testing123"
    },
    "standard": {
      "user": "test_user",
      "pass": "Testing123"
    },
    "standard2": {
      "user": "test_user2",
      "pass": "Testing123"
    }
  }

We need to use to cy.mysql_db() to automatically seed the users as the ones defined within this environment variable setup.

Should not be too hard since we can use REGEX replacement in the second "replace" parameter of cy.mysq_db(). Something like this:

REDCAP_USER/username

Where REDCAP_USER is the magic constant and username is the name passed in from a Cypress environment variable.

Shefali Mukerji

Operating System: CentOS 7 / PHP 7

Test Environment:
MacOSX 10.13 host operating system running Docker Container running CentOS 7 / PHP 7

Adam De Fouw

Operating System: CentOS 7 / PHP 7

Test Environment:

MacOSX Catalina 10.15 host operating system running Docker Container running CentOS 7 / PHP 7

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.