Hi Michael,

Just wanted to clarify somethings about the project acceptance tests. Firstly, I noticed in the marking rubric about corresponding to the top 70% of value. In the case of our client the $100 test was split evenly into 25/25/25/25 and was pretty adamant about changing allocation. Should we just leave it? Does this mean its not possible to achieve full marks?

And secondly about the location for each test description. Does this refer to the subsystem such as a database module or does it refer to the python or db file we are testing or have we completely interpreted it wrong?

Thanks a lot!

ANONYMOUS wrote:

Hi Michael,

Just wanted to clarify somethings about the project acceptance tests. Firstly, I noticed in the marking rubric about corresponding to the top 70% of value. In the case of our client the $100 test was split evenly into 25/25/25/25 and was pretty adamant about changing allocation. Should we just leave it? Does this mean its not possible to achieve full marks?

And secondly about the location for each test description. Does this refer to the subsystem such as a database module or does it refer to the python or db file we are testing or have we completely interpreted it wrong?

Thanks a lot!

Hi, What testing refers to in the documents are the acceptance tests that the Team negotiate with the Client. Of course there will need to be internal testing at the module level, but the user doesn't necessarily need to see them, unless they are particularly keen. In other words, the acceptance tests reflect how the user expects the system to work at the user level. The tests therefore are concrete examples of the specs in action.

Cheers MichaelW 👨‍🎨