Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test: improve coverage of acceptance testing #4043

Closed
1 task
kevinwhoffman opened this issue Mar 13, 2019 · 3 comments
Closed
1 task

test: improve coverage of acceptance testing #4043

kevinwhoffman opened this issue Mar 13, 2019 · 3 comments

Comments

@kevinwhoffman
Copy link
Contributor

Feature Request

User Story

As a Give developer, I want more acceptance tests to cover the most common Give user flows so that we can ensure bug-free releases and minimize our dependence on manual testing.

Possible Solution

Start by getting your local environment set up using this readme. Then proceed to write tests defined in the acceptance criteria below.

Related

#4039

Acceptance Criteria

  • A test confirms whether a logged-in user can successfully make a donation. (There are existing tests or logged-out users, but we specifically want to ensure that a logged-in user can donate).
@JasonTheAdams
Copy link
Contributor

@kevinwhoffman Getting myself going with the Jest tests. I have composer and everything going, but I can't seem to get the tests to run. The containers are running, but when I run npm run test nothing seems to happen in the container. I've tried running it headless and otherwise, no dice.

I may need a hand troubleshooting this when you have a few minutes to chat, unless someone else is familiar with the acceptance test workflow?

@JasonTheAdams
Copy link
Contributor

Well, I got jest to do something by running brew install watchman && brew upgrade watchman as learned from this issue: jestjs/jest#3436

However, the tests just fail for me. I have docker running and everything, but all the tests timeout and fail. I'll post back if I have any further success.

@DevinWalker
Copy link
Member

Closing this issue in favor of creating individual issues per necessary test.

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

No branches or pull requests

3 participants