Project

General

Profile

action #1310

Improve debugging capabilities for the tests

Added by aplanas over 6 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Feature requests
Target version:
-
Start date:
2015-04-28
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
Difficulty:
Duration:

Description

Once the test is running there is no way to know what is happening inside the test, or have a good knowledge of why the test fails. We need to provide tools to debug the test. These tools can include a debug console to print logs, or a way to inspect the execution of the test (traces, break points, etc).

Another solution is to integrate into the final video a WebVTT subtitle overlay to show the keystrokes in real time, allowing people to better understand what happens, when and why.

And a way to run again the tests, using a previous VM state


Subtasks

action #7328: os-autoinst: add fail reason for screen mismatchResolved

History

#1 Updated by coolo over 5 years ago

  • Category set to 138

#2 Updated by RBrownSUSE over 4 years ago

  • Category changed from 138 to Feature requests

#3 Updated by okurz over 4 years ago

  • Status changed from New to In Progress

aplanas wrote:

Once the test is running there is no way to know what is happening inside the test, or have a good knowledge of why the test fails. We need to provide tools to debug the test. These tools can include a debug console to print logs, or a way to inspect the execution of the test (traces, break points, etc).

Nowadays the logs include a lot of information from the executed tests including asserted screens and key presses.

And a way to run again the tests, using a previous VM state

Possible and properly documented, e.g. see the 'SKIPTO' flag and 'MAKETESTSNAPSHOTS' for creating qemu snapshots and restoring from them for fast re-execution. I consider this done.

#4 Updated by okurz over 4 years ago

  • Status changed from In Progress to Resolved

Also available in: Atom PDF