Hi!
Based on the feedback from users we've put together the second
chapter of the Test Management Tool guide: Let's together dive a
little bit more and look Under The Hood [0] of tmt to see how
plans, tests and stories work together on a couple of examples:
Plans [1] are used to enable testing an
Hi!
After the initial hint [1] describing the very first steps with
tmt let's have a look at the available test execution options.
The following user story was at the very beginning of tmt:
As a tester or developer, I want to easily run tests
in my preferred environment.
Do you want to s
Hi!
For those who still haven't heard: tmt [1] is now fully supported
in Packit [2], Fedora CI [3] and the RHEL CI. This means it is
possible to use the same concise and consistent config to enable
tests across all of them, more easily open source tests, share
test coverage across releases and run
On Wed, 3 Feb 2021 at 17:42, Petr Lautrbach wrote:
> Petr Lautrbach writes:
>
> > Kevin Fenzi writes:
> >
> >> Greetings everyone.
> >>
> >> We finally have everything in place and hopefully tested to make the
> >> switch tomorrow from master to rawhide/main branches for
> >> src.fedoraproject.
Hi!
> # Packages not included in mass rebuild?
>
> - tmt is newer in 32 than in 33:
> 0:0.20-1.fc32 > 0:0.19-1.fc33
Recently I was unable to build a fresh tmt package for rawhide
because of a missing build dependency:
https://koji.fedoraproject.org/koji/taskinfo?taskID=48098490
https:/
Hi Dominik,
Thank you for your questions. See my comments inline.
On Thu, 23 Jul 2020 at 14:39, Dominik 'Rathann' Mierzejewski
wrote:
>
> On Wednesday, 22 July 2020 at 14:49, Petr Šplíchal wrote:
> > Hi!
> >
> > I am writing today to share a proposal for how w
Hi!
I am writing today to share a proposal for how we can make it
easier to enable tests in Fedora CI.
We've heard the user story mentioned in the subject many times.
Fedora developers have frequently mentioned the difficulties which
they face with enabling tests in Fedora CI. Some people don't
u
Hi!
With a couple of qe & devel guys who are involved in the CI
effort we've started work on creating tmt, a tool for testing.
Why? We've got a bunch of dreams [1] and we would like to:
* run, debug and develop tests in much more comfortable way [2]
* open source more tests and run them closer to
On Thu, 11 Oct 2018 at 09:49, Richard W.M. Jones wrote:
>
> On Wed, Oct 10, 2018 at 11:26:01PM +0200, Miroslav Vadkerti wrote:
> > Hi,
> >
> > sorry for the late response :(
> >
> > On Tue, Oct 2, 2018 at 9:42 AM Richard W.M. Jones wrote:
> >
> > > On Mon, Oct 01, 2018 at 11:26:59AM +0200, Mirosl
On Tue, 21 Aug 2018 at 15:22, Jeremy Cline wrote:
>
> Hi Petr,
>
> On 08/21/2018 11:50 AM, Petr Šplíchal wrote:
> > Hi,
> >
> > as part of bringing upstream and downstream workflows related to
> > testing one more step closer together and allow easier automati
Hi,
as part of bringing upstream and downstream workflows related to
testing one more step closer together and allow easier automation
tools development and sharing between Fedora, Red Hat Enterprise
Linux and other products, the CI team is proposing to use a
consistent format for the CI related m
oject.org/tests/selinux/pull-request/1
[2] http://fmf.readthedocs.io/en/latest/examples.html#setups
[3] https://fedoraproject.org/wiki/CI/Metadata
On 23 January 2018 at 09:18, Petr Šplíchal wrote:
> Hi,
>
> simple proof of concept is ready for experimenting:
>
> https://
roject.org/wiki/CI/Standard_Test_Interface
[2] https://fedoraproject.org/wiki/CI/Share_Test_Code
psss...
On 1 March 2018 at 18:06, Honza Horak wrote:
> On 03/01/2018 04:00 PM, Petr Šplíchal wrote:
>>>>
>>>> To sum up what I've heard so far from the developer side
>> To sum up what I've heard so far from the developer side:
>>
>> * I would like to enable tests for my component (yes, I want)
>> * I will take care of them (really, I see the benefit in CI)
>> * I want to easily collaborate on tests with qe (direct commits)
>> * I don't want to give qe commit ac
> > > My worries are basically that this mechanism is hiding the
> > > tests from the package maintainers. It splits the concerns
> > > between people maintaining the artifacts and people
> > > maintaining the tests, which is exactly what the original
> > > plan to bring CI was *not* about.
> >
> >
On 22 February 2018 at 15:50, Pierre-Yves Chibon wrote:
> On Wed, Feb 14, 2018 at 05:28:20PM +0100, Petr Šplíchal wrote:
>> Hi!
>>
>> During the last days there have been concerns raised regarding
>> what is an appropriate content for the tests namespace. [1] My
>
On 14 February 2018 at 18:18, Adam Williamson
wrote:
> On Wed, 2018-02-14 at 17:28 +0100, Petr Šplíchal wrote:
>> Hi!
>>
>> During the last days there have been concerns raised regarding
>> what is an appropriate content for the tests namespace. [1] My
>> original
Hi!
During the last days there have been concerns raised regarding
what is an appropriate content for the tests namespace. [1] My
original idea was to enable sharing tests even across branches of
the same component, not only for tests to be used by completely
different packages. The initial exampl
Hi,
simple proof of concept is ready for experimenting:
https://github.com/psss/fmf
http://fmf.readthedocs.io/
Looking for the first impressions & feedback. Thanks.
psss...
On 8 January 2018 at 15:49, Petr Splichal wrote:
> Hi!
>
> In order to keep test execution efficient when numbe
Hi!
2016-06-02 13:35 GMT+02:00 David Kutalek :
>
> Hi,
>
> wrt psss - former email: pspli...@redhat.com:
>
> Afaik:
> - he would like to continue with did (with other e-mail address)
Yes, I'm taking did as my personal hobby project and will continue
with the development. Ondřej Pták offered help
20 matches
Mail list logo
