>  instead of references to servers that no longer exist is small projects
that can be uploaded as part of the spec

Not seeing how this will help, because this is application DEPLOYMENT
architecture issue. In this example, if you moved on from FTP hosting to
PaaS (eg. some apache shared host to Heroku), no matter what sample project
is supplied, there will be no way for volunteers to test it. Would need to
upload a whole VM with those environments.


вт, 16 окт. 2018 г. в 18:58, Glenn Holmer <[email protected]>:

> On 10/16/2018 04:12 PM, Rodrigo Teixeira Andreotti wrote:
> > I'm running PHP project tests on windows and linux and I came across a
> > small problem in test suites for projects from remote code, one of which
> > is that it is not clear in the test if there is any server to use during
> > testing (/Remote 1.png/), I tried to find the documentation that the
> > test indicates but could not find.
>
> I'm sure there are still some tests that depend on resources that are no
> longer available here at Apache.
>
> > I still managed to perform this test using my personal server along with
> > some projects I have.
>
> What we need instead of references to servers that no longer exist is
> small projects that can be uploaded as part of the spec. Testers could
> then download the project and use it for testing. The Free Form test in
> the Profiler spec is an example of a test that has a downloadable
> project. It would be great if you could come up with one, but you may
> want to save it for the next NetCAT (see below).
>
> > One last doubt, when a case test is updated by the team, do I have to
> > perform all the tests again?
> >
> > I did some testing on the projects in Java, but one got behind (skip)
> > because it lacked a file to download, but I can not get back in it to
> > mark it finished, I get the following warning:
> >
> >     Action failed Conflict: Structure of specification has changed since
> >     last testing and testing can not be resumed. Please use Restart
> instead
>
> Ideally, there should be no changes to a test spec once testing begins.
> I'm not sure how Synergy is meant to handle this if it's done anyway. I
> would say restart it (rather than resuming it) and pick up where you
> left off.
>
> --
> Glenn Holmer (Linux registered user #16682)
> "After the vintage season came the aftermath -- and Cenbe."
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>

Reply via email to