Machine Learning Development Testing
CT-AI · 15 questions
- An apiary winter-loss desk uses a popular ML development framework (TensorFlow or PyTorch named only as examples). A developer called an API in a way the library did not intend, and the fit looks “done.” What mitigation should testers pick?
- A library hold-time team picked a speech-oriented framework to rank tabular hold queues. Fits are clumsy and exports are wrong. What mitigation should testers pick?
- An avalanche-beacon desktop toolkit reports “ready,” but the build skipped a dependency and the first notebook cell dies. What mitigation should testers pick?
- A ferry-wait framework prints a glowing F1 that nobody can reproduce by hand on the same cells. What mitigations should testers pick for that defective evaluation implementation?
- A compost-odor lab’s framework takes minutes to return a one-row score, the screens confuse the seasonal crew, a shared notebook is world-readable, and the user guide is a stub. How should testers match those four framework risks?
- A street-tree failure desk suspects a defect inside a library the framework ships (the syllabus’s example is a defect in PyTorch). Two models that should agree do not, and the official metrics look impossible. Which mitigations should testers pick?
- A parking-occupancy lab used a clustering algorithm on labeled occupancy classes, guessed a learning rate, spilled the same rows into train and test, and called a two-fold split “k-fold.” Which named reviews and tests mitigate those four risks?
- A choir-attendance run looks brilliant on one random seed and collapses on the next; a packed file for the lobby kiosk was never re-scored; a new model is about to replace one that may already be better. How should testers map those three risks?
- An ice-fishing hut-permit kiosk must accept the MLS, pick up GPU-driver and framework dependencies, run the install script, and later uninstall cleanly in the shack and in the harbormaster closet. What should testers name that activity?
- A mushroom-ID handheld is one bad push away from stranding foragers. Testers want to know the previous model (or the whole pipe-plus-model) can be restored. When must rollback testing be performed?
- A hydrant-flow model is ready for the city. Testers will send only a small subset of live requests to the new model and watch latency, accuracy, and error rate before a full rollout. What should they name that activity?
- A pottery-glaze camera already serves the studio. Testers want the new model to see the same live frames without changing what the kiln board is told. What should they name that activity, and how does it differ from a canary?
- A swimming-center occupancy model is converted from its training format into a smaller file for the edge box. What should testers name the check after that format change?
- A salt-barn bag-count MLS is supposed to run on a clerk’s phone, an aisle edge box, and the town-hall server. What should testers name the check across that intended range?
- A telescope cloud-alert MLS publishes an interface that the night-shift feed, a volunteer app, and the data pipe must call. Testers need to check inputs, outputs, error messages, and those integration paths. What should they name that activity?