UI - DocumentsUI Framework

bcgov / entity

ServiceBC Registry Team working on Legal Entities

Apache License 2.0

23 stars 58 forks source link

UI - DocumentsUI Framework #22412

Closed arlentees closed 1 month ago

arlentees commented 1 month ago

Stand Alone | Proof of Concept

[x] Nuxt 3 (Looks like Nuxt 4 is still in dev) for Vite, Vitest, Vue3
[x] Look into Nuxt laying for NPM publishing
[x] Basic Routes and place holder components
[x] ~Import common components~ Not an import but a localized copy of whats been created by business-dashboard team

cameron-eyds commented 1 month ago

@arlentees Thank you!

cameron-eyds commented 1 month ago

@chdivyareddy As mentioned in stand up, not sure how we can QA this stuff until we have it deployed :D Any thoughts on this?

Maybe in this unique scenario we will need specific tickets for QA and UXA, following the PoC being deployed?

chdivyareddy commented 1 month ago

@cameron-eyds , Yeah I'm not sure how this can be verified...may be will need to wait until QA tickets are deployed:)

cameron-eyds commented 1 month ago

@arlentees There is a small concern it may be a bit before we get the PoC actually deployed and UXA'QA'Able. Are we opposed to creating a dedicated UXA/QA ticket that we can tackle once we are able to do so?

The main reason to do so would be for metrics essentially, ie moving tickets along and not lingering in staging for a few sprints, or however long it took to get to a deployed state.

arlentees commented 1 month ago

@cameron-eyds thanks for the heads up - I'm not too concerned about metrics, so having things hang around for a sprint doesn't sound bad to me. However, in this case, if the work for the POC isn't something that can be QA'd yet via normal pipelines and workflows, then one option could be to QA the work via a short demo to the team in a post-standup breakout session.

@HimaniTanwarGov do you have any thoughts on this?

HimaniTanwarGov commented 1 month ago

@cameron-eyds - I encourage to track the QA work in a ticket and if we are blocked (not able to work on it for any reason) I suggest we add a blocked tag to such Product Backlog Item. Or as @arlentees suggested - we can have a QA via short demo post our daily scrum. Which approach would bring the most value ?