ENGINEERING & PLANNING · LOCAL TOOL
LuniTestPlan
Build a test campaign. See the equipment conflicts. Replan when the day changes.
Schedules tests locally around working hours, dependencies and resource availability. A feasible schedule is not a guarantee of the best schedule.
Inputs stay in page memory. Save a plan file to keep your work; reopening it restores inputs, not a previously verified result. No automatic storage or uploads. Page and asset requests reach the host.
1. Working calendar
All dates are wall-clock planning times in one shared local calendar. No timezone conversion or DST adjustment. Tests must fit entirely within a single shift; no overnight shifts, pause/resume or holiday feed. Add holidays using equipment blackout intervals, or deselect their weekdays.
2. Equipment and people
Use a resource for each bench, device pool, operator or shared facility. Each test consumes one unit from every selected resource.
3. Tests
Use Ctrl/Command or Shift to select multiple resources/dependencies. Priority 9 is highest. A not-before time models a delay. A deadline is a hard finish limit. A locked start reserves an agreed slot; use it to preserve a completed or committed test in a replanning scenario.
Import tests from Excel / CSV
Headers: id,duration,resources,dependencies,earliest,deadline,lockedStart,priority. Duration in minutes; multiple IDs separated by |. Dates use YYYY-MM-DDTHH:MM. Blank optional date cells are allowed. Import replaces the test list only after validation; resources must already exist. CSV and tab-separated Excel rows are supported.
4. Equipment unavailable
Reserve units for maintenance, another campaign or a holiday. Overlapping intervals cannot reserve more than resource capacity.
Learn LuniTestPlan
Schedule and changes
Ready. Edit the sample and calculate.