Skip to content

reg.json is being generated with different capitalization of folder name resulting in matching new/deleted results in the report #522

@KociPApplifting

Description

@KociPApplifting

Describe the bug

The reg.json file shows different capitalization of folder "Form input" resulting in the Report showing (in my case) 124 new/deleted results.
Unfortunately i cannot provide lot of details about my env because of the nature of the project im working on, hopefully the screenshots and command im running will be helpful in isolating the issue, or maybe suggest what i can do on my end to avoid this.

Reproduced step

Steps to reproduce the behavior:

  1. Run "yarn run reg-cli spec/visual_component/actual spec/visual_component/expected spec/visual_component/diff -R spec/visual_component/componentVisualTestReport.html -J spec/visual_component/reg.json -M 0.1 || true" inside github action

Expected behavior

reg.json should show same capitalization of letters in the name of folders, as in generated expected/actual folders

Actual behavior

While folder names (and paths in general) are the same, reg.json is generated with different capitalization of /Form inputs/ and /Form Inputs/

Screenshots

These are the artifacts pipeline uploads after its finished

Here you can see the folders themselves are named correctly and match
Screenshot 2024-11-26 at 15 27 56

Here is inside of the reg.json where you can see different capitalization of /Form inputs/ and /Form Inputs/
Screenshot 2024-11-26 at 15 35 56

Here is resulting issue in the report:
Screenshot 2024-11-26 at 15 45 54

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions