Bug 807368 - Make TCMS to install special package from an extra repo
Summary: Make TCMS to install special package from an extra repo
Keywords:
Status: ASSIGNED
Alias: None
Product: TCMS
Classification: Other
Component: Usability
Version: 3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.0
Assignee: June Zhang
QA Contact: Nobody
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-27 15:38 UTC by Matěj Cepl
Modified: 2022-03-14 03:24 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)
working Beaker Job XML (3.75 KB, application/xml)
2012-03-27 15:39 UTC, Matěj Cepl
no flags Details

Description Matěj Cepl 2012-03-27 15:38:10 UTC
Description of problem:
I have this job in Beaker https://beaker.engineering.redhat.com/jobs/clone?job_id=209665 ... it works in Beaker, when I run it there, but I don't know how to make a test in TCMS to run it correctly.

The problem is that I use in the Job XML <repo> element and /distribution/pkginstall task (not mentioning a complicated method of selecting the machine).

When I put to the test case (see https://tcms.engineering.redhat.com/case/132982/edit/?from_plan=5258) running of the script /desktop/rhel6/xorg-x11-server/piglit all this will be ignored, right?

Version-Release number of selected component (if applicable):
beaker and TCMS as present on the Red Hat sites as of 2012-03-27

How reproducible:
100%

Steps to Reproduce:
1.see above
2.
3.
  
Actual results:
either it is not possible to install a special package from an extra repository or it is not documented

Expected results:
it should be possible and documented to run any working Beaker job (with its Job XML) via TCMS test.

Comment 1 Matěj Cepl 2012-03-27 15:39:01 UTC
Created attachment 573105 [details]
working Beaker Job XML

Comment 2 yawei Li 2012-05-16 08:54:53 UTC
integration with Beaker will be implemented in TCMS 4.0.


Note You need to log in before you can comment on or make changes to this bug.