if you're referring to gluon/tests/test_web.py they aren't (at least in travis-ci). you're required to have a running webserver in an outside process when launching test_web
On Tuesday, March 19, 2013 11:34:35 PM UTC+1, Massimo Di Pierro wrote: > > I do not believe the exec thing is any obstacle to testing. applications > can be tested in the same way. Current tests incude for example functional > testing for the registration and login process in welcome. > > On Tuesday, 19 March 2013 13:20:41 UTC-5, Richard wrote: >> >> I thougth that testing web2py was complexe because of the way the >> environnement was setup (execute)... >> >> So, how is travis-ci is working testing web2py and what the limitation of >> the test case for instance? >> >> Maybe the issue with testing is more for app then web2py it self? >> >> Thanks >> >> Richard >> >> >> On Tue, Mar 19, 2013 at 2:13 PM, Cliff Kachinske <[email protected]>wrote: >> >>> I saw a talk on Travis-ci last week. I think it's a great idea. >>> >>> You could also use it to test your own Web2py-based project and do your >>> system regression test using Selenium. >>> >>> >>> On Tuesday, March 19, 2013 11:31:06 AM UTC-4, Niphlod wrote: >>>> >>>> precisely. >>>> for 5-6 years old, it assures to run a set of commands in a fresh >>>> environment and logs the results. >>>> Given that we have some tests, and that those tests can be invoked, and >>>> that we **should** check if web2py works with python 2.5, 2.6, 2.7 it very >>>> useful. >>>> Additionally the travis environment ships with some "services" by >>>> default, and we're currently using postgresql and mysql to see if the DAL >>>> checks out, in addition to sqlite that has always been the "embedded" >>>> option. You all know that t-sql may differ, so we can check if any new >>>> feature committed to trunk is fine in nearly-real-time (can watch the >>>> status on the github page >>>> (https://github.com/web2py/**web2py<https://github.com/web2py/web2py>, >>>> see the green badge) or at >>>> https://travis-ci.org/web2py/**web2py<https://travis-ci.org/web2py/web2py>, >>>> >>>> if you click on the badge). >>>> >>>> tl;dr: travis-ci is saving developers from installing 3 python envs and >>>> 2 db engines to check if everything runs normally. >>>> >>>> PS: goes with the "announcement" that if tests cover what you need and >>>> what you use in your app, there will not be a new web2py release without >>>> those test pass completely (cause lazy developers can't hide anymore >>>> behind >>>> the "on my system it checked out correctly"). >>>> The "nice" addition, on the user-side, is that if you need some >>>> "feature" to be watched closely by the web2py team, you can submit patches >>>> or additions to the current tests suite: they'll get integrated in the >>>> mainline suite and travis will do the checks automatically. >>>> >>>> On Tuesday, March 19, 2013 4:06:51 PM UTC+1, Richard wrote: >>>>> >>>>> http://en.wikipedia.org/wiki/**Travis_CI<http://en.wikipedia.org/wiki/Travis_CI> >>>>> >>>>> I don't that much, but I would say that it is a motor to execute unit >>>>> tests so it make integration test finally. And I guess once you configure >>>>> your project to work with it each you commit something on github it will >>>>> execute all your unit tests and let you know that your build is good to >>>>> go >>>>> as long as your unit tests are up to date... >>>>> >>>>> Richard >>>>> >>>>> >>>>> On Tue, Mar 19, 2013 at 10:51 AM, Marco Túlio Cícero de M. Porto < >>>>> [email protected]> wrote: >>>>> >>>>>> Hi! >>>>>> >>>>>> forgive my ignorance.... what's Travis and what does it do ? >>>>>> (explanation for 3 year old if you can) >>>>>> Also, what benefits I can have by integrating it with Web2py ? >>>>>> >>>>>> Thanks for the info. >>>>>> Cheers, >>>>>> Marco Tulio >>>>>> >>>>>> >>>>>> 2013/3/18 Massimo Di Pierro <[email protected]> >>>>>> >>>>>>> Passes all tests using travis.ci including python 2.5/2.6/2.7 >>>>>>> sqlite/mysql/postgres. >>>>>>> >>>>>>> Thanks to Marc who originally pushed for travis.ci integration one >>>>>>> year ago and Niphlod for his help in getting this to work, explaining >>>>>>> it to >>>>>>> me like a three years old (and I needed the explanation), and for >>>>>>> fixing >>>>>>> all tests! >>>>>>> >>>>>>> https://travis-ci.org/web2py/**web2py<https://travis-ci.org/web2py/web2py> >>>>>>> >>>>>>> Massimo >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> --- >>>>>>> You received this message because you are subscribed to the Google >>>>>>> Groups "web2py-users" group. >>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>> send an email to [email protected]. >>>>>>> For more options, visit >>>>>>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>>>>>> . >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> []'s >>>>>> Marco Tulio >>>>>> >>>>>> -- >>>>>> >>>>>> --- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "web2py-users" group. >>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>> send an email to [email protected]. >>>>>> For more options, visit >>>>>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>>>>> . >>>>>> >>>>>> >>>>>> >>>>> >>>>> -- >>> >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "web2py-users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> >> >> -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
