[UserStory] Need acceptance test for product.

[AhmedSamay]

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 acceptance tests for the product
so that I can verify that QualityToolsExtension.jar is working properly with the BlueJ application.

Acceptance Criteria

(Rules or scenarios are acceptable formats.)

• Rule 1 [UserStory] QT4BJ extension has its own panel in BlueJ Preferences>Extensions #112 QT4BJ extension has its own panel in BlueJ.
• Rule 2 QualityToolsExtension.jar does not crash BlueJ application.
• Rule 3 [UserStory] QT4BJ extension appears in "Installed Extensions" window #113 QT4BJ extension appears in "Installed Extensions" window

Scenario 1

Given a gradle build
when the build is run
then then QualityToolsExtension.jar will display pass/fail on tests.

Supporting Information

(Relevant information, context, resources)

Dependencies

Depends On

(Issues on which this story depends) #112

Dependents

(Issues dependent on this story) #149

[holsappled]

I worked with #112 and #113 and wanted to share that a clear understanding of how to use the Gradle build and output of the QualityToolsExtension.jar needs to be understood. BlueJ provides a guide on how we moved forward with these dependency user stories.

https://bluej.org/extensions/writingextensions.html

[jody]

I'm confused by this User Story, including the title and story (which are non-specific) and the acceptance criteria (which cites user stories as rules and whose scenario is already met by the existing build process).

[AhmedSamay]

After discussion with shareholder, found User Story is irrelevant.