Skip to content

Create a test to check the issue #4501 #4532

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

Merged
merged 2 commits into from
Feb 1, 2018
Merged

Create a test to check the issue #4501 #4532

merged 2 commits into from
Feb 1, 2018

Conversation

paulovitin
Copy link
Contributor

Adds:

  • Check if after the user confirms the email and change the email again a new verification email is sent

Adds:
  - Check if after the user confirms the email and change the email
    again a new verification email is sent
@montymxb
Copy link
Contributor

montymxb commented Feb 1, 2018

Oh...well ignore what I was saying before. Didn't realize this was already up, totally missed that 🤣 . I'll suggest some changes here.

Copy link
Contributor

@montymxb montymxb left a comment

Choose a reason for hiding this comment

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

Alright, all I can think of is the clarification for test wording. Minus that, I like the test.

@@ -777,4 +777,63 @@ describe("Email Verification Token Expiration: ", () => {
});
});

it('When a user has verified their email, and then change it, the field emailVerified should be false and the new link will be send to the user', done => {
Copy link
Contributor

Choose a reason for hiding this comment

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

A suggestion to reword this to be a bit shorter

emailVerified should be set to false after changing from an already verified email

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Man, do you speak a lot hahaha.

@codecov
Copy link

codecov bot commented Feb 1, 2018

Codecov Report

Merging #4532 into master will decrease coverage by 0.08%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #4532      +/-   ##
==========================================
- Coverage   92.89%   92.81%   -0.09%     
==========================================
  Files         118      118              
  Lines        8445     8445              
==========================================
- Hits         7845     7838       -7     
- Misses        600      607       +7
Impacted Files Coverage Δ
src/Adapters/Cache/InMemoryCache.js 91.66% <0%> (-8.34%) ⬇️
src/RestWrite.js 93.1% <0%> (-0.73%) ⬇️
...dapters/Storage/Postgres/PostgresStorageAdapter.js 97.12% <0%> (-0.1%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 550b69e...d9695b7. Read the comment docs.

Copy link
Contributor

@montymxb montymxb left a comment

Choose a reason for hiding this comment

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

:octocat: fantastic! Although this behavior is already exhibited, now we'll be able to properly account for it in any further changes or releases from this point on.

@montymxb montymxb merged commit f2e21b0 into parse-community:master Feb 1, 2018
UnderratedDev pushed a commit to UnderratedDev/parse-server that referenced this pull request Mar 21, 2020
…existing (parse-community#4532)

* Create a test to check the issue parse-community#4501
* Check if after the user confirms the email and change the email again a new verification email is sent
* Change the spec text to requested in PR
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.

2 participants