Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[UserStory] DisPanel.java Unit Test #6

Open
3 of 5 tasks
BdwinE opened this issue Nov 6, 2019 · 2 comments
Open
3 of 5 tasks

[UserStory] DisPanel.java Unit Test #6

BdwinE opened this issue Nov 6, 2019 · 2 comments
Labels
user story User Story

Comments

@BdwinE
Copy link

BdwinE commented Nov 6, 2019

User Story

Essential components

  • Title describes the story
  • Stakeholder type is identified
  • Outcome is described
  • Rationale is explicit
  • Acceptance criteria are verifiable and from the perspective of the stakeholder

Story

As a maintainer
I want the DisPanel class to have a unit test
so that it will be easy to debug the code

  • Rule 1 Have a unit test for each method

Scenario 1

Given the DisPanel.java program
when A JUnit test hasn't been ran
then run a JUnit test

Depends On #4

@BdwinE BdwinE added the user story User Story label Nov 6, 2019
@BdwinE
Copy link
Author

BdwinE commented Nov 6, 2019

Assign to @BdwinE and @mbamiluka

@BdwinE BdwinE changed the title [UserStory] Dispanel.java Unit Test [UserStory] DisPanel.java Unit Test Nov 6, 2019
@BdwinE BdwinE changed the title [UserStory] DisPanel.java Unit Test [UserStory] #DisPanel.java Unit Test Nov 6, 2019
@BdwinE BdwinE changed the title [UserStory] #DisPanel.java Unit Test [UserStory] DisPanel.java Unit Test Nov 6, 2019
@BdwinE BdwinE changed the title [UserStory] DisPanel.java Unit Test [UserStory] [DisPanel.java](https://github.com/MetroCS/imagelab/blob/master/imagelab/DisPanel.java) Unit Test Nov 6, 2019
@BdwinE BdwinE changed the title [UserStory] [DisPanel.java](https://github.com/MetroCS/imagelab/blob/master/imagelab/DisPanel.java) Unit Test [UserStory] DisPanel.java Unit Test Nov 6, 2019
@jody
Copy link
Contributor

jody commented Nov 7, 2019

As presented, the Scenario provides no value and thus should be deleted.

Dependency is stated in the wrong direction (that his user story depends on #3). Change to state that User Story #3 depends on this user story. (That is, completion of #3 requires #6 to first be addressed.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
user story User Story
Projects
None yet
Development

No branches or pull requests

2 participants