On Tue, Feb 21, 2017 at 10:22 AM, Robert Sandell wrote:
> I think Jesse added some in the mercurial plugin when he extracted
> docker-fixtures from the ATH.
A work in progress but yes.
> And the ATH has plenty of examples as well as docker-fixtures itself
Right, this is
I just wrote one for my experimentation with the ldap plugin here
https://github.com/rsandell/ldap-plugin/commit/2c85eb0d3f258529562b111a75604e0af7a3486c
I think Jesse added some in the mercurial plugin when he extracted
docker-fixtures from the ATH.
And the ATH has plenty of examples as well as
Thanks for the suggestion. Any pointers to examples of cases which use
docker-fixtures as a test dependency?
Mark Waite
On Tue, Feb 21, 2017 at 6:45 AM Jesse Glick wrote:
> If Selenium testing is overkill, then just reproduce the bug in
> `git-plugin/src/test/`. You can
If Selenium testing is overkill, then just reproduce the bug in
`git-plugin/src/test/`. You can add a `docker-fixtures` test dependency if
it is helpful.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and
I’ll ask them, but from the past courses I can say that they will probably have
not enough time: most of them are doing their master in parallel to their
normal job.
(I am already very happy if they can spend a day per week for the project at
the least...)
> Am 16.02.2017 um 10:43 schrieb
I'm think that a Jenkins job which asserts the conditions related to a bug
report is a regression test. I admit that the Jenkins jobs I create are
not Selenium tests, and they do not require a web browser in order to run.
They are definitely not able to exercise JavaScript, and they do not
I would also much rather see a genuine regression test. If some aspect of
ATH is too weak to reproduce the bug properly, then that is what needs
fixing.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and
> Am 13.02.2017 um 20:39 schrieb Mark Waite :
>
> I'd love to have students help create Jenkins jobs which illustrate specific
> bugs in the git plugin, for example. Sample jobs which illustrate different
> bugs as Jenkins jobs are available from the
This looks somewhat too complicated for a course, would better fit for a
thesis…
> Am 13.02.2017 um 19:44 schrieb Victor Martinez
> :
>
> Maybe it is a bit out of the scope and I don't know whether there is already
> a ongoing testing framework for the
Hi Ulli,
Do you consider aligning these activities with Google Summer of Code?
Currently we are looking for project ideas, and actually test framework
improvements + test improvements could be a good project.
I understand that GSoC implies a significant time dedication by students,
which
I'd love to have students help create Jenkins jobs which illustrate
specific bugs in the git plugin, for example. Sample jobs which illustrate
different bugs as Jenkins jobs are available from the lts-with-plugins
branch of my docker repository. I've found it very powerful to have a
Jenkins job
Maybe it is a bit out of the scope and I don't know whether there is already a
ongoing testing framework for the pipeline. But, is it something feasible? It
might be a really good contribution to the community
Cheers
--
You received this message because you are subscribed to the Google Groups
In the summer semester I will again give a testing course here at the
University of Applied Sciences in Munich.
Several master students have the chance to improve their testing skills on a
real project: Jenkins.
The scope is integration and system testing (maybe also some unit testing if
there
13 matches
Mail list logo