Back in the olden days, when PhantomJS was replaced by cypress, the old tests were just ported to cypress conventions in a kind of hacky way to get them implemented. The tests are verifying that various JS functions are returning what are expected.
However, Cypress is designed as E2E tool and tests should be testing what is shown on the UI. Our tests aren't verifying UI at all.
To achieve this, we should have means to populate database with pre determined data and thus allowing Cypress to navigate to various UIs like forms and such and for example, test that autocomplete.js results are shown on the UI instead of just returning from the module.
Back in the olden days, when PhantomJS was replaced by cypress, the old tests were just ported to cypress conventions in a kind of hacky way to get them implemented. The tests are verifying that various JS functions are returning what are expected.
However, Cypress is designed as E2E tool and tests should be testing what is shown on the UI. Our tests aren't verifying UI at all.
To achieve this, we should have means to populate database with pre determined data and thus allowing Cypress to navigate to various UIs like forms and such and for example, test that
autocomplete.jsresults are shown on the UI instead of just returning from the module.