>>> A very interesting bit will be the "2.4.2 compat" and "dev" compat >>>> <snip> >>> >> >> Some late night quick hacking and I have come up with this proof of concept: >> >> https://www.travis-ci.org/nicoddemus/pytest-plugs >> >> As it is right now it serves only as a prove of concept, of course. The >> idea is using travis to handle running things for us, driving it using a >> script that downloads and run tests using tox. We can then collect json >> information from that and POST those results back to devpi. Also we can use >> its build matrix to test against different pytest versions, for example. > > Hum, interesting. Is this mainly to make use of travis-ci's build hosts? > What is the advantage over just invoking "devpi test PLUGIN-NAME" from the > script to automate the download/unpack/test/post-results steps?
I'd say the biggest advantage is to not execute stuff on your own server. They have to deal with that anyway. Regards, Florian Schulze _______________________________________________ Pytest-dev mailing list [email protected] https://mail.python.org/mailman/listinfo/pytest-dev
