captools / capcollector Goto Github PK

eg https://coveralls.io/

Tests run locally, even on headless firefox setup, but they do not run on Travis' setup.
Disabled in 5b36d7a

Right now it accepts any uid/password or even none.

Template fields should be validated when templates are added, both one-by-one and in bulk (eg, check polygon intersection, check placeholder format)

Authoring this on Eclipse in Fairfield.

1. The tool should facilitate that alert composition is chained into a review process (e.g., allow the draft alert to be e-mailed to colleagues or managers).
2. The alert composer should be able to work on the same alert in a series of sessions, and also to make a revised version of an alert received from another person.

For cancel alerts, should the tool be defaulting to 60 minute expiry, or should it set expiry = sent?

Different places do this differently. In the US and Canada, for instance, they will sometimes send a "This alert has expired" message that itself expires sometime in the future after it is presumed that everyone has seen that it's over, rather than just making the alert disappear.

Avoid specifying port both in settings_dev and on the runserver command line.

Fields like description and instructions aren't required, but the vast majority of alerts aren't useful without them. Provide a reminder in the UI if they are left blank or have minimal content.