Frontmatter
| title | docs(testplan): add comprehensive test plan for Label component (#7488) |
| author | Alachi24 |
| state | Closed |
| createdAt | Oct 19, 2025, 10:08 PM |
| updatedAt | Nov 9, 2025, 1:49 PM |
| closedAt | Nov 9, 2025, 1:49 PM |
| mergedAt | |
| branches | dev ← testplan_docs/label-component |
| url | https://github.com/neomjs/neo/pull/7548 |
Input from Gemini:
Hi @Alachi24, thank you for your contribution and for following the Hacktoberfest "Cookbook" epic (#7475) to create this test plan.
I've reviewed the PR and it looks like there has been a mix-up between two different components, which is an easy mistake to make.
Incorrect Component Target: The PR is for the "Label component" (
Neo.component.Label), but the test plan's acceptance criteria are for theTextfield (Neo.form.field.Text). It seems you may have accidentally used the example from the cookbook epic, which was for the Text field, as the basis for your plan. Could you please generate a new test plan that is specifically forNeo.component.Label? It's a much simpler component, so the plan will be shorter.Unrelated
package.jsonChanges: This PR also includes large changes topackage.jsonandpackage-lock.json. These files should not be modified in a documentation PR. Please revert the changes to these two files so that the PR only contains the new test plan markdown file.If you'd like to create the test plan for
Neo.form.field.Textinstead, that's perfectly fine too! Just let me know, and we can update the PR's title and description accordingly.Once these issues are resolved, I'll be happy to review it again. Thanks for your efforts!
@tobiu , Please, due to recent changes, I noticed the epic cookbook I need for references is no longer under the ISSUES folder.
can you direct me to its new location? This is what I'm referring to: .github/ISSUE/epic-cookbook-create-test-plans.md
Well, this is related to the new 2-way sync. all locally saved tickets now have the format issue-<gh-id>.md
I have tried checking all the issues and I didn't see the epic cookbook which is needed for the task to commence. Really challenging @tobiu
the cookbook is this one: https://github.com/neomjs/neo/issues/7475. it should also be inside your fork, in case you update it and search for the id 7475 inside .github/ISSUE.
It has been worked on, please look at it and confirm if it's on track. @tobiu
i would add to update the text config at run-time, to verify that the DOM updates. To get the PR accepted, please remove the package.json and package-lock changes. thx.
It's done. kindly confirm @tobiu
take a look at: https://github.com/neomjs/neo/pull/7548/files => still shows 3 files instead of one.
inside your fork, you could just rollback the 2 files that should not be inside this PR and then do another commit.
@tobiu I have tried rolling back, but the thing here is, only the required file for PR was pushed, the package-lock and package.json weren't involved. I have resorted to deleting the whole package file on this particular branch, but it still shows 3 file changes.
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
The PR fulfills these requirements:
📝 Summary
This PR adds a detailed test plan outlining inherited behavior scenarios for the Label component
(Neo.form.field.Text). It ensures consistent functionality, predictable DOM behavior, and compliance with Neo’s framework standards.🔄 Changes
.github/ISSUE/ticket-cpm-test-component-label.mddisabled,hidden,cls, andstyleconfigurationsvalueconfig)isDirtyflag change detection💡 Impact
Other information:
This PR is part of the Hacktoberfest 2025 initiative to improve test coverage and developer documentation across the Neo.mjs component library.
Markdown preview: ticket-cpm-test-component-label
Closes #7488
Please, your review is needed @tobiu