Rewrites unit tests for FirstStep.vue

[JackieBinya]

Fixes

Fixes to #148 by @JackieBinya

Description

• After evaluating the problems with the FirstStep.spec.vue file. I decided to rename it to FirstStep1.spec.vue and created a file ~/test/unit/specs/FirstStep.spec.vue and rewrote all the tests completely. Coverage for the unit tests now is 100%

Tests

• Checkout git branch bg-first-step-unit
• On the terminal run the command npm run test:unit FirstStep1.spec.js to run the old unit tests
• The to run the new unit test run the command npm run test:unit FirstStep.spec.js
• To check the coverage run the command npm run test
• If you are happy with the implementation then you delete the old tests.
• To run e2e tests for the component run the command npm run test:e2e -- --tag first on the terminal

Screenshots

The Problem

The solution

Note

• the failing test is the old renamed unit tests i.e FirstStep1.spec.js
• new tests are listed in the table under components, row FirstStep.vue

Checklist

• My pull request has a descriptive title (not a vague title like Update index.md).
• My pull request targets the master branch of the repository.
• My commit messages follow best practices.
• My code follows the established code style of the repository.
• I added tests for the changes I made (if applicable).
• I added or updated documentation (if applicable).
• I tried running the project locally and verified that there are no
  visible errors.

Developer Certificate of Origin

Developer Certificate of Origin

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open-source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

[obulat]

Great start, @JackieBinya ! Could you please delete the old file and lint your tests (there are some quotes, extra spaces etc problems).

[obulat]

Both attributionHeader and ccLicenseHeader basically contain the same text, because parent div of h5 (attributionHeader), and the both should be visible, whether you click yes, no, or don't click at all. What you should better check for is the text inside them: is it Attribution or Creative Commons license.

[obulat]

Next button is always visible, but it is disabled before you click yes/no, you can test for that before/after you click on radio buttons.