Testing / PractiTest Interview Questions
Why do teams use Milestones to organize testing rather than filters alone?
Filters organize entities by any field value, but they don't inherently represent a time-bound goal the way a Milestone does.
- A Milestone explicitly represents an objective with a defined timeframe, like a sprint or release
- Requirements, Test Sets, and Issues can all be directly linked to the same Milestone, giving one unified view of everything relevant to that goal
- Dashboards can be built specifically around Milestone progress, showing overall readiness rather than just a filtered list
In practice, teams often use both together: filters to organize the day-to-day grid view, and Milestones to track whether a specific sprint or release is actually ready to ship.
What do filters lack that Milestones explicitly provide?
Do teams typically use filters and Milestones together, or exclusively one or the other?
More Related questions...
