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

help5501

This forum is provided to promote discussion amongst students enrolled in CITS5501 Software Testing and Quality Assurance. If posting a question, it's suggested you check first whether your question is answered in the unit Frequently Asked Questions (FAQ) list, and use the search box (on the right) to see if an answer to your question has already been posted.

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.

Note that any posts must comply with the UWA Code of Conduct and the UWA Academic Conduct Policy. That means you should (a) treat everyone with respect and courtesy, and (b) not post your solutions to an assessment that's in progress.

If asking a programming question, it's recommended you read How do I ask a good question? If reporting or troubleshooting a bug in software used in the unit, it's recommend you read How to report bugs effectively.
Displaying selected article
Showing 1 of 147 articles.
Currently 38 other people reading this forum.


 UWA week 41 (2nd semester, week 11) ↓
SVG not supported

Login to reply

👍x1
helpful
4:07pm Fri 11th Oct, ANONYMOUS

When asking a question about the unit content, it's always better to show some initiative and say what you think should be the case, but why you're unsure. Point to particular bits of the unit content or prescribed readings that are relevant, and explain what it is about them that's unclear. This not only helps you get an answer quicker, it helps improve the unit content, if something in the content is contradictory or unclear.

Hi Arran,

I share some concerns raised by OP regarding the project specification. The instructions ask us to "apply input space partitioning to the constructor," but they don’t clarify what exactly we should test — specifically, what we should design test cases for. Consequently, I’ve assumed that our responsibility is limited to testing the behavior of the LightingCommand constructor itself. However, I’m unsure if this is the correct interpretation, which has led to some confusion.

My understanding is that we are not responsible for validating Location, LightSource, or State objects in the test cases. If these objects are not null when they are passed to the LightingCommand constructor, they should be considered valid; otherwise, their corresponding constructors should have thrown an error. Additionally, as we learned in class, Java APIs generally assume that parameters are non-null unless explicitly specified otherwise.

As a result, I am having trouble with identifying three distinct characteristics for LightSource. While there are three parameters, I cannot partition the values for LightSource because, based on my understanding, it only needs to be valid. I considered comparing the expected state with the current state of LightSource, but since there’s no available code to retrieve the current state, it appears impossible to write code for the corresponding test case.

I would greatly appreciate your clarification on whether I’m approaching this correctly. Many of us are facing tight schedules as the semester concludes, and I’ve noticed that Q7 has caused confusion among several students. Since Q8 depends heavily on the outcome of Q7, it would be helpful if you could point out where I might be misunderstanding the requirements or suggest a different approach I should consider.

Thank you for your assistance.

The University of Western Australia

Computer Science and Software Engineering

CRICOS Code: 00126G
Written by [email protected]
Powered by history
Feedback always welcome - it makes our software better!
Last modified  8:08AM Aug 25 2024
Privacy policy