1
0
mirror of https://github.com/Unleash/unleash.git synced 2025-01-01 00:08:27 +01:00
unleash.unleash/src/test/e2e
Thomas Heartman 0a43d341c0
fix: check whether a usage data is defined (#5393)
The previous check would return `false` if the value was 0, causing a
bug where the usage data wouldn't be included.

This also adds tests to ensure that usage data for CR segments is
propagated correctly because that's where I first encountered the issue.

Before this fix, if the values were 0, the data would display like the
bottom element in the screenshot:


![image](https://github.com/Unleash/unleash/assets/17786332/9642b945-12c4-4217-aec9-7fef4a88e9af)
2023-11-27 11:20:25 +01:00
..
api fix: check whether a usage data is defined (#5393) 2023-11-27 11:20:25 +01:00
helpers feat: feature type updated audit log (#5415) 2023-11-24 14:24:31 +01:00
routes fix(tests): correctly set baseUriPath in setupAppWithBaseUrl (#5068) 2023-10-18 13:17:56 +02:00
seed
services fix: User audit events (create, update, delete) should include rootRole. (#5399) 2023-11-24 16:06:37 +01:00
stores test: speed up the tests (#5140) 2023-10-24 14:31:38 +02:00
custom-auth.test.ts fix: User audit events (create, update, delete) should include rootRole. (#5399) 2023-11-24 16:06:37 +01:00
dedupe-permissions.e2e.test.ts fix: dedupe any duplicate permissions (#5397) 2023-11-23 10:23:21 +00:00
health.e2e.test.ts
migrator.e2e.test.ts test: silent migration test (#5131) 2023-10-23 17:14:41 +02:00