metasfresh / metasfresh-e2e-legacy

metasfresh End-2-End Testing project.
7 stars 1 forks source link

Make sure fixtures are used in tests and not overwritten #286

Closed metas-dh closed 5 years ago

metas-dh commented 5 years ago

Test shall include:

Atm we use fixtures in most of our tests; however, they are set at the beginning of the test but get overwritten later on with randomized values (usually sth like e.g. "TestName" plus Timestamp). To adapt the tests to customer data, we need to make sure that the fixtures are not overwritten at some point in the test, so that we can use customer-specific fixtures (plus Timestamp, so that the tests can run >1 time).

For that,

  1. the fixtures we have atm need to be renamed: the fixture shall have the same name as the test (e.g. taxrate.json becomes taxrate_setup_spec.json)
  2. the objects used in the tests need to be adapted
  3. the tests need to be adapted

⚠️ The test that i modified for the drafts is: cypress/integration/price/add_a_product_to_a_pricelist_schema_and_create_a_new_PLV.js (check it to see how many things have to be changed in either variant)

Todo for developer (besides coding)

All Flags are ticked? Congratulations, you have delivered!

TheBestPessimist commented 5 years ago

I think we can close this issue now, since both me and @cristinastefan90 have moved (pretty much?) all the tests to use data from fixtures instead of harcoded data.