I am trying to keep it intentionally small and the API may change. For example I am going to refactor some of the decorators as bottle plugins. About your questions. we will continue use travis-ci like we do with web3py. I like behave but may people I talked too found it hard to learn and that is contrary to web2py/web2py philosophy. If we can integrate web3py+behave+selenium using a SDL it would be a great way to generate tests for apps, not for web3py itself.
On Saturday, 30 March 2019 23:48:10 UTC-7, Christopher Smiga wrote: > > Hi Massimo and Team, > > It's been a several years since contributing to the project, and I'm > interested in web3py for several reasons such as > > * it is a fresh project > * speed > * architecture improvements > * the future of web2py > > In this effort, are pyunit (TDD), Python Behave Library (BDD), CI/CD, > performance testing, functional testing, and code integrity via SonarQube > being considered in the build process? > > Web3Py has the potential of being the next world class web framework. What > is the plan for development of this new endeavor since automation test > development is important? > > Thanks and regards, > Christopher Smiga > SDET (Software Development Engineer in Test) -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
