How to Test Major Changes to CSS - TACC/Core-CMS GitHub Wiki

Confirm similar or identical build output for project(s) on default branch versus the branch to test.

When checking out branches:

• If branch has change to dependency or version of dependency, then run npm ci.
• If branch has change to taccsite_custom, then run git submodule update.

0. Clean out any previous testing you may have done with these steps.

   git rm -rf taccsite_cms/static/site_cms/css/build-for-compare

1. Confirm CSS on default branch builds for frontera-cms.

   Follow default branch's instructions to build for Frontera CMS. (No need to collectstatic.)

2. Copy build output to new directory, and stage the change with Git.

   rm -rf taccsite_cms/static/site_cms/css/build-for-compare
   cp -r taccsite_cms/static/site_cms/css/build taccsite_cms/static/site_cms/css/build-for-compare
   git add taccsite_cms/static/site_cms/css/build-for-compare

3. Confirm CSS on new branch builds for frontera-cms.

   Follow new branch's instructions to build for Frontera CMS. (No need to collectstatic.)

4. Replace that copied old build output with new build output (do not stage).

   rm -rf taccsite_cms/static/site_cms/css/build-for-compare
   cp -r taccsite_cms/static/site_cms/css/build taccsite_cms/static/site_cms/css/build-for-compare

5. Compare the build outputs via git status.

   pwd # confirm you are at CMS repo root
   git status

6. Confirm you see only relevant staged changes.

   • (via git status) You should see "Changes to be committed" for build-for-compare/.
   • (via git status) You may see "Changes not staged for commit" for build-for-compare/.

   
   The test instructions that led you to this document will clarify whether you should see "Changes not staged for commit" (represents build output change) and if so, what should have changed.

7. Clean out new branch's built CSS.

   git rm -rf taccsite_cms/static/site_cms/css/build-for-compare
   npm ci

8. Confirm CSS on default branch builds for core-cms.

   Follow default branch's instructions to build for Frontera CMS. (No need to collectstatic.)

9. Copy build output to new directory, and stage the change with Git.

   rm -rf taccsite_cms/static/site_cms/css/build-for-compare
   cp -r taccsite_cms/static/site_cms/css/build taccsite_cms/static/site_cms/css/build-for-compare
   git add taccsite_cms/static/site_cms/css/build-for-compare

10. Confirm CSS new branch builds for core-cms.

    Follow new branch's instructions to build for Frontera CMS. (No need to collectstatic.)

11. Replace that copied old build output with new build output (do not stage).

    rm -rf taccsite_cms/static/site_cms/css/build-for-compare
    cp -r taccsite_cms/static/site_cms/css/build taccsite_cms/static/site_cms/css/build-for-compare

12. Compare the build outputs via git status.

    git status

13. Confirm you see only staged changes.

    • (via git status) You should see "Changes to be committed" for build-for-compare/.
    • (via git status) You may see "Changes not staged for commit" for build-for-compare/.

    
    The test instructions that led you to this document will clarify whether you should see "Changes not staged for commit" (represents build output change) and if so, what should have changed.

14. Repeat as desired for each project.