Skip to content

Issues: zsoldosp/django-performance-testing

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

8 Open 4 Closed
8 Open 4 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Django 2 support help wanted
#30 opened Jun 14, 2018 by rafaelcapucho
4
support combining multiple result files into a single one a'la coverage
#22 opened Jun 28, 2017 by zsoldosp
warn/fail when a limit is specified for an unknown settings based limit
#18 opened Jan 19, 2017 by zsoldosp
support displaying the actual queries that failed the limit
#16 opened Nov 24, 2016 by zsoldosp
support setting_changed test signal for settings.DJPT_KNOWN_LIMITS_DOTTED_PATHS
#12 opened Nov 3, 2016 by zsoldosp
use the registry for setting up the collectors with id_
#11 opened Nov 3, 2016 by zsoldosp
WorstReport shouldn't include ad hoc limits with heading 'None' bug
#6 opened Oct 4, 2016 by zsoldosp
allow adding a unique name/context to Limits to aid context manager based ad-hoc debugging
#5 opened Oct 4, 2016 by zsoldosp
ProTip! Type g p on any issue or pull request to go back to the pull request listing page.