You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the bottom, it says "The technique described in How to Simulate HTTP Authentication in a Functional Test is cleaner and therefore the preferred way." Why should we document something that's not recommended?
The technique doesn't look clean at all.
The text was updated successfully, but these errors were encountered:
I dislike the "Auth with a token" tutorial a lot. However, in complex applications the alternative "Auth in tests" technique doesn't work. I always see the first technique implemented.
In any case, I'd merge both articles and add a brief explanation about when to use each of them.
…cation (javiereguiluz, HeahDude)
This PR was merged into the 2.7 branch.
Discussion
----------
Merged and improved the articles about testing + authentication
This fixes#6741.
Commits
-------
fc8e8c6 Fixed status code test
be5fe37 Improved a test
211da90 Merged and improved the articles about testing + authentication
I propose to delete the "How to Simulate Authentication with a Token in a Functional Test" cookbook article:
The text was updated successfully, but these errors were encountered: