Age | Commit message (Collapse) | Author | |
---|---|---|---|
2018-04-21 | Add parallel test processors (#7215) | Yamagishi Kazutoshi | |
2018-04-11 | update gem, test pam authentication (#7028) | Alexander | |
* update gem, test pam authentication * add description for test parameters * fix inclusion of optional group | |||
2018-03-04 | Provide default OTP_SECRET value for development environment (#6617) | Akihiko Odaki | |
2017-04-15 | Add recovery code support for two-factor auth (#1773) | Patrick Figel | |
* Add recovery code support for two-factor auth When users enable two-factor auth, the app now generates ten single-use recovery codes. Users are encouraged to print the codes and store them in a safe place. The two-factor prompt during login now accepts both OTP codes and recovery codes. The two-factor settings UI allows users to regenerated lost recovery codes. Users who have set up two-factor auth prior to this feature being added can use it to generate recovery codes for the first time. Fixes #563 and fixes #987 * Set OTP_SECRET in test enviroment * add missing .html to view file names | |||
2016-11-29 | Update .env.test | Eugen | |
2016-11-24 | Add .env.test | Alyssa Ross | |
It took me ages to get Mastodon set up with the tests passing because the environment variables I needed to define weren't documented and I had to work them out one at a time. This change adds a .env.test file, and makes it so it isn't ignored by git. I think it makes sense for the .env.test file to be in git, since there's nothing secret in it, but other approaches would be to have a .env.test.sample (like the corresponding one for production), or to set these values in a test helper, or to adapt the tests to work with environments other than this one. I'd be happy to make these changes if that would be preferred. Being able to get set up and run the tests is a pretty important part of being able to contribute to Mastodon (or your test coverage with suffer!), so having some sort of solution like this one is vital. |