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

hypothesis / h / 8380 / 1
67%
master: 97%

Build:
Build:
LAST BUILD BRANCH: realtime-update-v1-h-only-1
DEFAULT BRANCH: master
Ran 05 Oct 2015 09:36AM UTC
Files 84
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

05 Oct 2015 09:29AM UTC coverage: 67.176% (+0.01%) from 67.166%
8380.1

push

travis-ci

seanh
Fix database drop table issue with tests

Tests were getting a "cannot drop table "user" because other objects
depend on it" error if you ran just one test module (that tries to use
the database) on its own.

I think the problem is basically that a given models_test.py is only
importing the ORM classes from its corresponding models.py and not those
from other models.py modules that may depend on them and that may exist
in the test database.

Calling reflect() before drop_all() causes sqlalchemy to go and find
these other database tables and ORM classes, then it can correctly drop
them all.

2376 of 3537 relevant lines covered (67.18%)

0.67 hits per line

Source Files on job 8380.1
  • Tree
  • List 0
  • Changed 1
  • Source Changed 1
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 8380
  • Travis Job 8380.1
  • 5eea2aa0 on github
  • Prev Job for on kill-sqlite (#8376.1)
  • Next Job for on kill-sqlite (#8382.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