- Add a template filter and use it for the gauge
- Return KiB in implemented models
- Fix the tests accordingly

Fix #157

Fix #172

No implementation change

The `manage.py` contains a generic `test` method.

Ref #189
Ref #188

Ref #189

Ref #189

This is just to avoid the warning.  Track modifications don't affect us
anyway, since they only apply when one wants to make use of tracking
changes in the model.  It will in future releases be disabled by default
according to the warning.

Adding an extra config in the ini style is still supported, but will be
replaced by something better soon.

Also, test `location_log_config` for None, because `isfile` does not
accept `None` as a path.

Refs #190

Sentry is now being initialized before the default and additional log
configs are applied.  This has the advantage that in the near future,
when an additional `dict` config can be provided, such handlers can be
added by will.

Currently, only one `Sentry` instance is assumed, located at
`app.extensions['sentry']`.  Consequently, every `SentryHandler`
returned by the handler-creating callable is linked to the latter.

Making this possible required a small patch.  See the docstring of
`replace_empty_handler_callables`.

Usage in a dict logging config: See `sipa.defaults.DEFAULT_CONFIG`.

Refs #190

Refs #190

This is a message concerning the initialization of the app.  I think
this better fits into the `DEBUG` layer.

Since we don't actually care about the implementation (“was `.json`
called?”, “Was a `ValueError` catched?”, …), we don't need to mock the
`Response` object and all of its functions.

The better approach is to let the mocked `get`-function return an actual
`Response` object, and setting the binary content (`content` is a
property, thus `_content` is set).

Now, the test only has to verify whether the binary represantation of a
json-dump of a dict is being read into the same dict again.

It is more consequent to check explicitly for 'get' and 'post' as the
`method`-argument for `do_api_call`.

Also, add a test for the invalidity of something else.

Also, put the `gerok` and `sample` tests into their own module.

Fix #194

Using `list` would cause (under certain circumstances) the test to fail,
just because the position of the returned elements in the list is
different.  Obviously, this is not what we want to test.

Forgetting this somehow bricked the abc-mechanism, which is not
surprising, since not using `functools.wraps` for a decorator is
foolish.

SPOILER ALERT: I'm to blame.

What this ought to do was exactly the same as what `id` does.  The
difference is: one is being used, the other – not so much.

This fixes the tests that got `broken` by actually fixing the
`active_property` decorator in the previous commit.

Lucky me.

- Add the test structure, i.e. `TestGerokUser` class with example user,
  `User` comparison method and api mock

- Add test testing an explicit creation via `__init__`

- Update the fake API to correctly parse the given query string
  (This was to add `find?ip={}` query functionality)

- Test user creation via `User.from_ip`

- Rename `id` to `user_id` where necessary (id is a builtin function)

- In `User.from_ip`, the constructor `cls()` has been called with
  a *completely different* signature, which last commit's test showed.

- In the same run, cache the name on explicit user creation, and include
  `realname` in the tests.

It makes far more sense to pass the whole (and often used) `user_data`
dict instead of the isolated parameters `name` and `mail`.

In the gerok module, the `mail` field of the API's `userdata` JSON-dict
is supposed to be the redirection mail address.  Thus, if it is empty,
the `user.mail` property should contain the builtin mail address of the
gerok module.

The tests were extended so this usecase is in `assert_userdata_passed`.

Funnily, the inline `if` statement got parsed correctly.

The fake api got extended by the used `find?login=` functionality, a
corresponding test for `user.get()` has been added.

This includes:

- a fix in the `userData` comparisons asking whether nothing came
  back (`if not` is correct for the empty string, `do_api_call` never
  returns `None`)

- a fix in the fake api concerning not being given an existent IP

- a test with a few foreign IPs checking for `AnonymousUserMixin`.

This is mostly implementation in the `fake_api`, the test itself is just
an `AssertEqual`.

Extensively test correct availability of traffic data in `gerok.User`.

The `user_data` being used in the `TestGerokUser` Case is now created as
a mixture of the cartesian product of certain edgecases (combinations of
missing traffic entries, 0-2 hosts) and an iterating, and thus unique,
part contributing attributes like `name` and `password`.

The assertions concerning the traffic entries belong in their own test.