Faculty of Engineering and Mathematical Sciences 
Not logged in (login)


This forum is provided to promote discussion amongst students enrolled in CITS5501 Software Testing and Quality Assurance.

Before posting a question here, you might like to (1) search the forum for previous posts asking the same question, and (2) read the article How To Ask Questions The Smart Way .
And please keep the discussion civil (as required by UWA's Computer Use Policy, #9).

RSS cloud
Jump to:


1 of 124 articles shown, currently no other people reading this forum.
From: Arran S.
Date: Wed 27th May 2020, 1:24pm



When we looked at Input Space Partitioning, we said that there are a few good places to 
look when trying to come up with characteristics. So in your explanation of why a 
characteristic is appropriate, you might just appeal to one of those.

If you just give a characteristic with *no* explanation of how you got it, that won't in 
general be considered a very good answer.

Apologies, but it's hard to be more specific than that without further information.

If you like, you can email me the example you're thinking of, and I can at least say 
whether or not it is totally off-track as a justification.




> Hi, 1d states that we should "Explain why they (characteristics) are appropriate,
> and how you would use them in writing unit tests." Is there any justification we 
> should be looking at in particular in this case?

Related articles

1d (both) RSS
├─ original   Wed 27th May 2020, 1:16pm, ANONYMOUS
└─ THIS   Wed 27th May 2020, 1:24pm, Arran S.
This Page

Program written by: [email protected]
Feedback welcome
Last modified: 11:27am Sep 21 2020