With Cypress, you can easily create tests for your modern web applications, debug them visually, and automatically run them in your continuous integration builds.

Cypress Community

were you able to solve the problem?

there are few bunch of questions I have for this.. firstly IMHO as best practice I believe describe defines a test suite. You should only have one top-level test suite per file, and only one domain per test.

I would just change those describes to contexts and wrap the contexts in a single describe. 

Correct me if I am wrong if I misunderstood your problem but as you probably know cypress more than me but as soon as cypress starts the tests it tries to get the number of tests in the spec and the ```data``` object defined initially is taken and thus the element ```el``` takes the value from that. However if you ```cy.log(data);``` in your first it() you will see that you are getting the correct data after before. So I believe it is working as designed

So basically your object should be finalized before cypress test execution starts if you want your data.forEach to get the final changes, having it in before probably wont work

try moving the object assignment outside of before() directly to  describe that should work