Skip to content
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.

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

Default strategies for more Django model field types #642

Closed
Zac-HD opened this issue May 23, 2017 · 0 comments
Closed

Default strategies for more Django model field types #642

Zac-HD opened this issue May 23, 2017 · 0 comments
Assignees
Labels
enhancement it's not broken, but we want it to be better

Comments

@Zac-HD
Copy link
Member

Zac-HD commented May 23, 2017

There are several types of fields that we don't have a default strategy for, and it would be good to fix that.

Notes: some fields can just be added to the default mapping; others have extra metadata (eg length of strings, digits of decimals) to exploit. All exceptions should inherit from HypothesisException. We shouldn't try to generate autofields or file-related fields. There's some scope for reorganising the code (eg exception classes at the top, alphabetise fields, etc).

@Zac-HD Zac-HD added enhancement it's not broken, but we want it to be better help-wanted labels May 23, 2017
@Zac-HD Zac-HD self-assigned this Jun 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement it's not broken, but we want it to be better
Projects
None yet
Development

No branches or pull requests

1 participant