On 8 Sep 2015, at 17:42, Nick Boldt wrote:
Re: jbosstools-discovery/pull/299 nothing pings those URLs.
only there so when a user clicks on a certification link for more
info, they get a page opened in a browser. None of the install tests
will catch what happens when a user clicks on a "more info" link. :D
Yes, and that is my point. Some test should do that.
If we keep fixing bugs without adding tests we'll keep failing.
Re: jiras for install grinder, yes. There are a few. There are also
Okey - so what is the status it ?
On Mon, Sep 7, 2015 at 3:52 AM, Max Rydahl Andersen
> We have our install-grinder and p2 install tests to catch errors but
> I don't notice them being mentioned when what looks like actual basic
> errors are fixed.
> i.e. https://github.com/jbosstools/jbosstools-discovery/pull/299
> issue, simple fix.
> But was this caught by p2 install and install-grinder ?
> - if not, why not ? This seems like one that should have been easily
> - if yes, why first now ? We made this change to sites a while ago
> (JBDS-3208 was resolved end-of-june)
> Looking at the logs of install-grinder
> it shows perfect blue since Jun 13 2014.
> So my assumption is that it was *not* caught.
> Nick/Mickael - how come install-grinder can pass when the repos it is
> supposed to point to are 404 ?
> If it's because the tests are using intermediary build urls then it
> sounds like we are missing an actual test for the
> released bits as opposed only having for our current build ?
> jbosstools-dev mailing list
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio