[Help wanted] Write proper unit test instead of verifying checksum with fromJS

[kopax]

Update unit test for css mixins

We did validate our function using their checksum after validation for all historical unit test.

Reason: when we started @bootstrap-styled/v4, styled-components v1.0 was missing descent test utils and IDE integrations. This was often causing invalid css due to missing trailing comma in our code.

Checksum was a way to multiple check any code change throung test update requirement.

New test css utils for styled-components now exist such as:

• https://www.styled-components.com/docs/api#test-utilities

This already appeared in package.json and is not used (yet), @santaclauze (wait for explanation):

    "stylelint": "^9.9.0",
    "stylelint-config-recommended": "^2.1.0",
    "stylelint-config-styled-components": "^0.1.1",
    "stylelint-processor-styled-components": "^1.5.1",

We must stop maintaining our tests using CSS checksum and check the css synthax with it.

This is not urgent but maintaining CSS the current way is a slow down factor for every modifications. It also doesn't make sens anymore.

Related Issues

• How can I test valid CSS string for styled-components that it is not rendered with wrong/invalid css values? styled-components/styled-components#2298

Solution

Every time a change needs to be made on @bootstrap-styled/css-mixins, everytime a new test is added, this issue will collect explanation and test example from the test author. This will increase XP sharing for testing CSS across our team.

This ticket will be closed when no more checksum unit test will be existing in our source code.

[kopax]

Example of test improvement:

• 37ae5c9#diff-dc012ba2bcaadead24bc3c0e576a5800
• 37ae5c9#diff-dc012ba2bcaadead24bc3c0e576a5800
• 37ae5c9#diff-d674b0f1c4baa1e1be12bfd8bffb8b41
• 37ae5c9#diff-9b566524498893746f7df3babfc5dcd6