Skip to content

feat: Add data-testid attributes to improve testability

Edouard Legoupil requested to merge add-data-testid-attributes into main_dev

Created by: Edouard-Legoupil

Added data-testid attributes to various components in the frontend to facilitate more reliable Playwright testing. This change addresses the difficulty of selecting elements that lack stable identifiers.

Key changes:

  • Added data-testid to interactive elements in Chat.jsx, KnowledgeCard.jsx, Review.jsx, and their sub-components.

  • Updated the CreatableSelect component in KnowledgeCard.jsx to use inputId and classNamePrefix for better testability with react-select.

  • Does my code meet the quality standards for releasing packages?

  • Does the reviewer have all the information to validate the features/issues without too much research?

  • Does the customer who will validate the associated tickets have the information to do so without wasting time?

Issues to validate to close :

  • issue #

Processed issues to keep open or in progress:

  • issue #

Checklist:

  • Does the package check go local?
  • Does the CI pass?
  • Are the added / fixed features documented, tested?
  • Are the added features / solved problems briefly presented in the PR message?
  • Are the changes related to tickets / issues that I have listed in the commits and in the PR itself?
  • Are the tickets in "review" mode in the Project Tracking Board?
  • Does each ticket, if it is to be closed after acceptance of the PR, contain a comment that tells how to validate it?

Merge request reports