help3200

It's UWAweek 42 (2nd semester, week 12)

help3200

This forum is provided to promote discussion amongst students enrolled in CITS3200 Professional Computing.

Please consider offering answers and suggestions to help other students! And if you fix a problem by following a suggestion here, it would be great if other interested students could see a short "Great, fixed it!" followup message.

How do I ask a good question?

Displaying selected article

Showing 1 of 127 articles.
Currently 84 other people reading this forum.

UWA week 33 (2nd semester, week 4) ↓

Project Acceptance Test (all 6)

9:53am Mon 12th Aug, Michael W.

"Mitchell Otley" <23*7*7*5@s*u*e*t*u*a*e*u*a*> wrote:

> I have a similar, related question - for the test description part, do we need to have all the information regarding input data, output data, procedures (i.e. a test script) in there as well? Or can we just have a description of what the test will cover, and then update the extra information in a later sprint?

Hi Mitchell, Rephrasing what I said in reply to Devarsh's question, the set of tests should be what the client wants to see to convince themselves that that system does what they requested it to do. BTW, the Team should, independently, put in place systematic lower level (ie module level) testing as well. The client may, or may not, be interested in that level of detail, but it will make it more certain that everything will work, and the embarassing, "hold it while we fix this" moments are avoided. Cheers MichaelW 👨‍🎨 Cheers MichaelW

help3200 articles all ANNOUNCEMENTS recent articles login to post a new article help3200 topics from today and yesterday from the past week from the past two weeks ALL topics, most recent first	login chapter0 unitinfo research projects csforum csse-feedback csbreakdown cssubmit csmarks 2nd semester help fora Algebra Advanced Algorithms Cloud Computing High Performance Computing Intelligent Agents Professional Computing Relational Database Management Systems Systems Programming