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

Null values in equivalence partitions #192

Open
KendrickAng opened this issue Nov 26, 2019 · 4 comments
Open

Null values in equivalence partitions #192

KendrickAng opened this issue Nov 26, 2019 · 4 comments

Comments

@KendrickAng
Copy link

Should null values be included in equivalence partitions, or are they trivial enough to exclude from EPs? When should we include, or exclude them?

@damithc
Copy link
Collaborator

damithc commented Nov 26, 2019

When an input is possible to be null, it should be considered. For example, when testing a Java method that has an int parameter, it is not possible for that input to be null as Java would not allow null for an int input.

@tcgj
Copy link

tcgj commented Nov 26, 2019

Does this mean that if it's an non-primitive object type, like String or Task etc, the only partitions are null and not null

@damithc
Copy link
Collaborator

damithc commented Nov 26, 2019

Does this mean that if it's an non-primitive object type, like String or Task etc, the only partitions are null and not null

Testing would be much easier if that were the case :-)

not-null objects have state (i.e., attribute values), and can belong to different partitions based on the state. For example, a String object can be alpha-numeric or not alpha-numeric, a Person object can be sick or healthy and so on.

@tcgj
Copy link

tcgj commented Nov 26, 2019

Good point. Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants