rats_install scheduling disabled
by Kamil Paral
After discussion with hongqing I disabled rats_install test in commit 531830e. It is too outdated and doesn't currently work. Hongqing plans to update it in the future and then we can re-enable it.
commit 531830e (HEAD, refs/remotes/origin/master, refs/remotes/origin/HEAD, refs/heads/master)
Author: Kamil Páral <kparal(a)redhat.com>
Date: Fri Nov 25 10:37:51 2011 +0100
rats_install: disable scheduling
This test is outdated and doesn't work at the moment. We need to update
it first. Untill then let's keep it disabled.
12 years, 5 months
[AutoQA] #389: add function to get window position into LDTP
by fedora-badges
#389: add function to get window position into LDTP
----------------------+-----------------------------------------------------
Reporter: hongqing | Owner:
Type: task | Status: new
Priority: major | Milestone: Automate installation test plan
Component: core | Keywords:
----------------------+-----------------------------------------------------
The cursor should be captured when the guest's virt-viewer window pops
up, so the terminal arguments can be typed in. LDTP offers the function to
get the window size, but do not offer
function to get the window position. So it is impossible to calculate the
coordination the the mouse should click.[[BR]]
We will contact with the LDTP team to develop a such function or submit a
patch for them.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/389>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
12 years, 5 months
[AutoQA] #388: parse the Fedora Installation Test Automation output as test results
by fedora-badges
#388: parse the Fedora Installation Test Automation output as test results
----------------------+-----------------------------------------------------
Reporter: hongqing | Owner:
Type: task | Status: new
Priority: major | Milestone: Automate installation test plan
Component: core | Keywords:
----------------------+-----------------------------------------------------
The output of Fedora Installation Test Automation project includes two
parts:[[BR]]
1.The terminal output got by serial port are stored in boot.log,
stage1.log and stage2.log[[BR]]
2.The anaconda logs are transferred by virtio, they are also stored in the
test results directory.[[BR]]
The test result 'PASS' or 'FAIL' can be got from the terminal logs, the
anaconda logs can be sent as attachments when the test fails. [[BR]]
These should be implemented in anaconda_install.py
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/388>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
12 years, 5 months
[AutoQA] #387: move analog into lib/autoqa and solve the path problem
by fedora-badges
#387: move analog into lib/autoqa and solve the path problem
----------------------+-----------------------------------------------------
Reporter: hongqing | Owner:
Type: task | Status: new
Priority: major | Milestone: Automate installation test plan
Component: core | Keywords:
----------------------+-----------------------------------------------------
the rsyslog template file analog is moved into lib/autoqa, the logging.py
in lib/autoqa will
call and run it directly. [[BR]]
when AutoQA is ran separately by run install.py or is ran by host 'autoqa
post-iso-build', the path of analog is different. This should be solved to
make sure AutoQA can be ran in both ways.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/387>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
12 years, 5 months
[AutoQA] #182: Write virt management script
by fedora-badges
#182: Write virt management script
----------------------------+-----------------------------------------------
Reporter: kparal | Owner:
Type: task | Status: new
Priority: major | Milestone: Virtualization
Component: infrastructure | Version: 1.0
Keywords: |
----------------------------+-----------------------------------------------
We must write a virt management script that will be able to the basic
tasks for us:
* query for available virt systems that we can use
* switch between "real" disk and a disk snapshot for a virt system
* revert a disk snapshot for a virt system
* perform some command in a virt system - e.g. "yum update" for keeping
it periodically up-to-date
* install/reinstall a virt-system for us with specified distro
* (some more to come?)
We may want to use some pre-defined names syntax to recognize what virt
systems do we have. For example:
{{{
/dev/vg_autoqa/F12_i686_1
/dev/vg_autoqa/F12_i686_1-snap
}}}
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/182>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
12 years, 5 months
[AutoQA] #254: Trasnfer autoqa library to autotest clients
by fedora-badges
#254: Trasnfer autoqa library to autotest clients
-------------------------+--------------------------------------------------
Reporter: kparal | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: autotest | Keywords:
-------------------------+--------------------------------------------------
Currently autotest clients do not require autotest package installed,
autotest server transfers all necessary files over rsync. But autotest
clients require autoqa installed (because of our autoqa libraries), which
in turn requires autotest.
This creates quite a lot of confusion where to edit which files when
testing new stuff. It would be much easier if we somehow transferred also
the autoqa library together with autotest files. Can we bend autotest a
little to rsync also our library to the client? Or, can we use similar
approach as copying the config files to the test directory also with
autoqa library? It would be great.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/254>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
12 years, 5 months
[AutoQA] #386: autoqa should use rotate logs
by fedora-badges
#386: autoqa should use rotate logs
-------------------------+--------------------------------------------------
Reporter: tflink | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: 0.7.0
Component: core | Keywords:
-------------------------+--------------------------------------------------
As currently configured, autoqa does not use logrotate. This means that
all logging will keep going to the same file and that file will keep
getting bigger and bigger.
In order to keep the logs at a sane size, it would be nice to use
logrotate or something with similar functionality.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/386>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
12 years, 6 months
