0057648: data-testids are not consistent across different keypads

Description

Most keypads in POS have the same data-testid structure. For example:

- The data-testid of the key '1' ends with 'num1' in all keypads
- The data-testid of the key '2' ends with 'num2' in all keypads

However, the data-testid of the key '.' ends with 'action6' in some keypads, but it is 'action3' in others, which is not consistent.

This inconsistency prevents us from testing some keypads and functionalities correctly with Cypress, which is the goal of the data-testids.

Steps To Reproduce

These steps just guide you through the POS to verify different keypads, so that you can see their different test-ids.

1) Log in POS
2) Add a product to the ticket
3) Click the ticket line
4) In the pop-up, click the quantity
5) In developer tools, verify that the '.' button's data-testid ends with action6
6) Click OK
7) Select 'Price Modification'
8) In developer tools, verify that the '.' button's data-testid ends with action6
9) Click OK
10) Select 'Discount'
11) Select 'disc-5-var-perc'
12) In developer tools, note that the '.' button's data-testid ends with action1, which is different from the previous ones
13) Click OK and Apply
14) Click Pay
15) In developer tools, verify that the '.' button's data-testid ends with action6
16) Select Cash, then Done, then None
17) Go to close till
18) In developer tools, note that the '.' button's data-testid ends with action3, which is different from the previous ones

Tags

No tags attached.

Attached Files

Relationships [ Relation Graph ] [ Dependency Graph ]

Notes
(0177598) hgbot (developer) 2025-03-27 12:19	Issue exported to Jira: https://openbravo.atlassian.net/browse/RM-24335 [^]

Issue History
Date Modified	Username	Field	Change
2025-01-15 10:34	asier_perez	New Issue
2025-01-15 10:34	asier_perez	Assigned To	=> Triage Platform Base
2025-01-15 10:34	asier_perez	OBNetwork customer	=> No
2025-01-15 10:34	asier_perez	Triggers an Emergency Pack	=> No
2025-01-15 10:34	asier_perez	Severity	trivial => minor
2025-03-27 12:19	hgbot	Note Added: 0177598
2025-03-27 12:19	hgbot	Status	new => closed
2025-03-27 12:19	hgbot	Resolution	open => duplicate