| Modifier and Type | Field and Description |
|---|---|
static float |
MAX_GENERATED |
static float |
MIN_GENERATED |
| Constructor and Description |
|---|
FloatNumericCase() |
| Modifier and Type | Method and Description |
|---|---|
Case<Float> |
excluding(Iterable<Float> values) |
Set<Subcase<Float>> |
getSubcases()
Returns the specific set of subcases that describe all equivalency classes for this case.
|
Case<Float> |
greaterThan(float minExclusive) |
Case<Float> |
greaterThanOrEqualTo(float minInclusive) |
Case<Float> |
inRange(float minInclusive,
float maxInclusive) |
Case<Float> |
lessThan(float maxExclusive) |
Case<Float> |
lessThanOrEqualTo(float maxInclusive) |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, waitexcluding, excluding, generateAllOnce, generateAllOnce, generateAnyOnce, generateAnyOnce, or, orNullpublic static final float MAX_GENERATED
public static final float MIN_GENERATED
public Set<Subcase<Float>> getSubcases()
CaseCases are expected to return at least one subcase. When the fuzzy engine is determining how many test cases to execute, it does so in terms of subcases, not cases. Thus, when using the pairwise permutation algorithm, the fuzzy library works to ensure that each possible combination of two subcases are executed.
Note to implementors: cases should generally not include null values as
possible outputs. Instead, consumers are expected to use the Case.orNull() method (or, equivalently,
Any.nullableOf(com.redfin.fuzzy.Case<T>)) to declare that their cases should also generate null values.
getSubcases in interface Case<Float>Copyright © 2017 Redfin. All rights reserved.