From: Alex Brandt <alunduil@gentoo.org>
To: gentoo-user@lists.gentoo.org
Cc: James <wireless@tampabay.rr.com>
Subject: Re: [gentoo-user] automated code validation
Date: Thu, 04 Dec 2014 13:02:55 -0600 [thread overview]
Message-ID: <3306609.71mJRjCGqA@elijah> (raw)
In-Reply-To: <loom.20141201T175046-420@post.gmane.org>
Hey James,
I've removed the original content for length but I love the
ideas you've put together for an overarching testing strategy.
I've begun work on a small ebuild testing framework, etest [1],
that I believe fits into your model quite well. It uses docker
images for isolation and repeatability. It allows developers to
verify the install time and some run time behavior of ebuilds in
an automated fashion. It's also extremely alpha and I find new
issues every time I use it.
That all being said I would love feedback and if anyone is brave
enough to use it I would love to start cataloging issues that
people find in github.
James, if this doesn't fit your vision then I apologize for the
tangential reply to your thread.
[1] https://github.com/alunduil/etest
Thanks,
--
Alex Brandt
Cloud Evangelist for Rackspace and Developer for Gentoo
http://blog.alunduil.com
next prev parent reply other threads:[~2014-12-04 19:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 17:40 [gentoo-user] automated code validation James
2014-12-04 19:02 ` Alex Brandt [this message]
2014-12-04 19:36 ` Alec Ten Harmsel
2014-12-04 21:03 ` [gentoo-user] " James
2014-12-04 21:08 ` [gentoo-user] " Rich Freeman
2014-12-04 21:41 ` Alec Ten Harmsel
2014-12-05 14:05 ` [gentoo-user] " James
2014-12-05 14:55 ` Rich Freeman
2014-12-05 16:31 ` James
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3306609.71mJRjCGqA@elijah \
--to=alunduil@gentoo.org \
--cc=gentoo-user@lists.gentoo.org \
--cc=wireless@tampabay.rr.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox