419
59%
master: 57%

Ran 25 Apr 2016 09:08PM UTC

Jobs 2

Files 48

Run time 42s

Badge

Embed ▾

pending completion

Build # 419

Build Type

push

travis-ci

Committed by

sh4nks

Commit Message

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))

Run Details

1982 of 3375 relevant lines covered (58.73%)

1.17 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	419.1	25 Apr 2016 09:08PM UTC	0	58.67	Travis Job 419.1
2	419.2	25 Apr 2016 09:08PM UTC	0	58.55	Travis Job 419.2

Source Files on build 419

Detailed source file information is not available for this build.

sh4nks / flaskbb / 419
59%
master: 57%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 419

sh4nks / flaskbb / 419 59% master: 57%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 419

sh4nks / flaskbb / 419
59%
master: 57%

README BADGES
x