248/test sequencer

[SimaoBolota-MetaCell]

Implemented solution: The objective was

• to add the testSequencer that allows tests to be ran alphabetically and sequentially
• to add test case for logging in to the application, when applicable

Sanity checks:

• The pull request is explicitly linked to the relevant issue(s)
• The issue is well described: clearly states the problem and the general proposed solution(s)
• From the issue and the current PR it is explicitly stated how to test the current change
• The labels in the issue set the scope and the type of issue (bug, feature, etc.)
• All the automated test checks are passing
• All the linked issues are included in one milestone
• All the linked issues are in the Review/QA column of the board
• All the linked issues are assigned

Breaking changes (select one):

• The present changes do not change the preexisting api in any way
• This PR and the issue are tagged as a breaking-change

Possible deployment updates issues (select one):

• There is no reason why deployments based on CloudHarness may break after the current update
• This PR and the issue are tagged as alert:deployment

Test coverage (select one):

• Tests for the relevant cases are included in this pr
• The changes included in this pr are out of the current test coverage scope

Documentation (select one):

• The documentation has been updated to match the current changes
• The changes included in this PR are out of the current documentation scope

Nice to have (if relevant):

• Screenshots of the changes
• Explanatory video/animated gif

[filippomc]

Thanks @SimaoBolota-MetaCell, dropped a few questions

[filippomc]

What is sharding and why is this part commented?

[SimaoBolota-MetaCell]

From my understanding sharding allows for a test suite to be split into arbitrary chunks. It's useful for lengthy test suites, not the case here. Then tests are identified via shardIndex/shardCount.
I left the sharding commented since it was part of the TestSequencer code in the Jest docs. Since the tests aren't being split using shard flag when I ran the tests with or without the sharding section, everything worked as intended.

FYI - Info that I found on sharding:

• https://medium.com/@mfreundlich1/speed-up-your-jest-tests-with-shards-776e9f02f637
• https://jestjs.io/docs/configuration#testsequencer-string

[filippomc]

Are tests sorted alphabetically?

[SimaoBolota-MetaCell]

Yes they are sorted alphabetically. The default sort order is ascending, built upon converting the elements into strings so it works as well if the tests are numbered.