• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

sh4nks / flaskbb / 419 / 1
59%
master: 57%

Build:
Build:
LAST BUILD BRANCH: new-theme
DEFAULT BRANCH: master
Ran 25 Apr 2016 09:08PM UTC
Files 48
Run time 2s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

25 Apr 2016 09:06PM UTC coverage: 58.667% (-0.001%) from 58.668%
419.1

push

travis-ci

sh4nks
Further work on the activate account functionality

I have renamed this functionality to "Activate Account" which I think
fits much better. In addition to that, I also make use of Flask-Login's
``is_activte`` method. I am not completely sure if I should go this
route like I did by simply adding a check in the User's model to see if
the admin activated this option (activate_account) AND if the user has
activated his account by following the instructions sent to him by email
and thus sets the property ``user.is_activate`` to True. The other
option would be to just force the login (e.q. login_user(force=True))

1980 of 3375 relevant lines covered (58.67%)

0.59 hits per line

Source Files on job 419.1
  • Tree
  • List 0
  • Changed 6
  • Source Changed 6
  • Coverage Changed 6
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 419
  • Travis Job 419.1
  • 798dd039 on github
  • Prev Job for on authentication-revamp (#415.1)
  • Next Job for on authentication-revamp (#421.1)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc