You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The method is not supposed to behave differently based on the string contents. Therefore, it is not necessary to consider empty string as a separate partition. But when choosing values to test, one can include a string with leading/trailing spaces to catch a bug caused by an unwanted trim() method in the code.
The other three partitions seem good enough.
Thanks Prof! On a similar note, how much should we use boundary values in testing? For instance, if n (int) has valid values in range [0,10] and we are asked to create test cases in an effective and efficient manner, what values should be considered?
Depends on how many test cases we can afford. Then, start with the boundaries (e.g., 0, 10), and then add non-boundary values (e.g., 4) if there is room.
I have a question regarding the equivalence partition of
text
in the above question. Currently, I have the following:Firstly, is an empty string a partition, since it also falls under option 2?
Secondly, are there any other partitions that should be considered?
The text was updated successfully, but these errors were encountered: