← Back to Difficulty Selection
Code Review (Easy): Sequencing the Pipeline
Story
Lena is working on a utility for the internal platform that helps the team cycle through different testing sequences for their microservices. Mark reviewed the initial draft and suggested that the tool should always find the next logical arrangement of IDs to ensure every unique combination is tested in order. If the team has already reached the very last possible sequence, the utility needs to reset the IDs back to their original, lowest order. For example, if a developer is currently looking at sequence 2, 3, 1, the helper should automatically shift it to 3, 1, 2 for the next session.
Your Task
Read the story and code, then decide if the code is ready for production or needs improvement.
Hints
What would block an approval? Give me a hint.
Next
Check out Next Topic: Symmetry in Asset Tags