Why you see something on a test environment every two weeks.

In our projects, new work is on a test environment every two weeks. You click through it yourself and approve it in My CodeIQ. That way you don't end up with software that works differently from what you intended after a few months.

Anna SminkPlanning and coordination3 minute read
Team around a table with laptops, someone points at sticky notes on the wall

What is on the test environment

The test environment is a copy of your platform with test data. Every two weeks we put the work that was finished in that period there. For each part, My CodeIQ shows what it does and what you can test.

How you approve it

You click through the new parts with the people who will be working with them. If it is right, you approve it in My CodeIQ. If something is missing or works differently than you expected, you add a comment. The developer who built it picks it up.

Developers at a long wooden table with laptops

What it does for the planning

A comment after two weeks costs a few hours. The same comment after six months sometimes costs weeks, because other parts have been built on top of it in the meantime. By looking every two weeks, the planning stays right.

I keep track of which parts are waiting for approval. If something has been waiting for more than a week, I give you a call.

Going live

What you have approved, we put live at a time we agree on together. After each phase you see what has been spent and decide with us on the next phase.

Portrait of Anna Smink
Written by

Anna Smink

Planning and coordination

Anna takes care of planning and administration. When something has been promised, she keeps track of whether it happens.

More about Anna

Share this article

LinkedInEmail

The coffee is already on.

Bring your question, your process or an idea that is not finished yet. In a first conversation we map out your situation and you get honest advice on the next step.

Freshly made

How do you take it?