consul/grecia
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Add expectations in tests confirming account

Browse Source 
One of these tests has failed once because there wasn't a user with the
right confirmation token. While I haven't been able to reproduce the
issue, there's a chance it's caused by a `visit` call to the
confirmation path which might start before the redirect request to the
successful sign up page has finished.

I'm not sure this is the case, though, but, worst case scenario, if the
test fails again we'll know it isn't because of a missing expectation.
This commit is contained in:
Javi Martín
2022-11-28 12:57:35 +01:00
parent 937a86e345
commit e68c22bb38
2 changed files with 5 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
spec/system/multitenancy_spec.rb
View File

@@ -129,6 +129,8 @@ describe "Multitenancy", :seed_tenants do
check "By registering you accept the terms and conditions of use" check "By registering you accept the terms and conditions of use"
click_button "Register" click_button "Register"
expect(page).to have_content "You have been sent a message containing a verification link"
confirm_email confirm_email
expect(page).to have_content "Your account has been confirmed." expect(page).to have_content "Your account has been confirmed."

3
spec/system/users_auth_spec.rb
View File

@@ -392,6 +392,9 @@ describe "Users" do
fill_in "Username", with: "manuela2" fill_in "Username", with: "manuela2"
click_button "Register" click_button "Register"
expect(page).to have_content "To continue, please click on the confirmation link that we have sent you via email"
confirm_email confirm_email
expect(page).to have_content "Your account has been confirmed" expect(page).to have_content "Your account has been confirmed"