You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Known-file picker in the test-script file actions. The UPDATE file / READ file step editor's path field gains the selector the APDU builder's
SELECT rows use: the file-manager tree, the custom files and the standard
file list (uicc_files.json), grouped by root with a filter, filling the
path. Only EFs are offered (the action reads/writes a file; a DF/ADF is not
a target); the text field stays authoritative, so a name path or a file the
lists do not carry can still be typed, and the picker preselects the current
path when it is known.
The live load-test stats now include the timing: while a script or suite
run repeats, the run banner (visible on every Test-script view), the
script editor's result head and the suite summary show the elapsed time,
the average per completed iteration and the estimated time left,
recomputed on every status poll (testLoadTiming/testRunBannerText; the
final report keeps the server's elapsed_ms/avg_ms). No completed
iteration yet means no bogus average/estimate - only the elapsed time.
Changed
The load-test iteration cap is raised to 1,000,000,000 (from 1,000,000) in
both layers: the PWA's TEST_ITERATIONS_MAX and the two field max
attributes, and the server's _TEST_LOAD_MAX. The value is well inside the
JavaScript safe-integer range (2^53-1), so the counters and the progress
display stay exact; the practical ceiling is the run duration (at 50 ms per
iteration the cap is ~1.6 years).