lp:testmanager

Branch merges

Propose for merging

No branches dependent on this one.

Related source package recipes

1 recipe using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

89. By Javier Collado on 2011-11-03

Modules that were missing added to the reference

autodoc warnings fixed

classes the inherit from gi.repository classes added to the patching
class so that they return object class and autodoc works (it doesn't
work with metaclasses)

88. By Javier Collado on 2011-11-03

KeyPath tests to check get item/slice added

87. By Javier Collado on 2011-11-02

Tab and LeftTab test cases splitted into different test suites

This modification makes clearer that LeftTab is the one that takes
care of the name and description fields, while Tab just provides the
basics for the creation of other tabs.

What this change doesn't add is a test case to create a result tab
since this isn't as easy as create one of the other tabs. This will be
fixed in a future commit.

86. By Javier Collado on 2011-11-01

Use Notebook.open_tab instead of Tab.create

Since open_tab just requires the row to be opened, the test code is
more readable.

85. By Javier Collado on 2011-11-01

Suite and invetory tabs moved to their own files

Given that the code for all tabs is growing, this is a good idea to
keep tab.py file not very long.

84. By Javier Collado on 2011-10-29

Gtk Manual plugin now can run cases and display results

A dialog similar to what checkbox provides is opened in the machine
where the server process is running. The response is sent back to the
client where the comment added by the tester can be reviewed.

83. By Javier Collado on 2011-10-28

command added as a field to the automatic runner results

The command itself is considered part of the results and, thus, is
added to them. The reason for this is that the command in the test may
change after the test is executed so when looking at the result the
case isn't a reliable source of information to know what command was
really executed.

In the future maybe some version control will be implemented so that
results might point to a test case and a revision number, but that's
not possible currently.

82. By Javier Collado on 2011-10-28

Result UI displays results from text runners

Automatic runner expanded with a RunnerResultUI class to display the
results stored by the test runner.

Result tab moved to its own module (result.py)

81. By Javier Collado on 2011-10-27

RunnerUI renamed to RunnerCaseUI

This is a preparation for a new class that will be called
RunnerResultUI. Since there will be more than one UI class this change
makes the naming a little bit more consistent.

Also, RunnerCaseUI has two new methods:
- get_name: Get name runner based on class name. This is useful to
create a UI class properly based on the runner name.
- get_ui_filename: Get the ui filename for this class. Probably this
will be refactorized in the future (like _get_all and _get_name) since
it's quite likely that RunnerResultUI will use it too.

80. By Javier Collado on 2011-10-26

socket.error exception captured

When there isn't any network connection and name server is not running
in the loopback interface, a socked.error exception will be raised
when trying to locate the name server using a broadcast message.

This change just captures the exception and logs the error the same
wasy as all other networking errors.