patternfly / patternfly/chatbot
Test additional edge cases for components we already have tests for
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6
- Forks
- 37
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 5
Description
To make sure our APIs stay stable, there's a few tests we could add for each of these components/props:
-
AttachmentEdit
-
Check if isOpen = false
-
filename
-
code
-
title
-
Chatbot
-
classname
-
innerRef
-
CloseButton
-
ariaLabel
-
ChatbotHeaderMenu
-
tooltipProps
-
menuAriaLabel
-
innerRef
-
ChatbotHeaderOptionsDropdown
-
tooltipProps
-
className
-
menuToggleAriaLabel
-
ChatbotHeaderSelectorDropdown
-
value
-
className
-
tooltipProps
-
menuToggleAriaLabel
-
tooltipContent
-
MessageBox
-
announcement (may be hard to test - don’t worry if impossible)
-
aria label
-
className
-
position - but may be hard to test - ok if impossible
-
PreviewAttachment
-
code
-
isOpen
-
title
Jira Issue: PF-1558
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the existing tests for AttachmentEdit, Chatbot, CloseButton, ChatbotHeaderMenu, ChatbotHeaderOptionsDropdown, ChatbotHeaderSelectorDropdown, MessageBox, and PreviewAttachment. Add coverage for the listed props and edge cases, skipping cases the issue identifies as potentially impractical, and run the existing test suite to confirm the APIs remain stable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100