~ In arrivo la prima beta di Android 11 ~
#R#OOS
Mancano 6 giorni alla pubblicazione ufficiale della prima beta release della nuova versione di Android. Dopo avervi segnalato la possibilità che nello stesso giorno possa uscire una build per i dispositivi OnePlus (qui), vi segnaliamo che è stato pubblicato il programma ufficiale del keynote:
• Alle 17 si inizia con la presentazione della nuova versione del robottino verde.
• Successivamente verrà proposto un Q&A con il vicepresidente e il senior director del team Andorid.
• Infine verrano caricati 12 talks (previsti per il Google I/O) nel quale verranno discusse molte tematiche del mondo Android.
Fr3ud
https://code.tutsplus.com/tutorials/behavior-driven-development-in-python--net-26547
Behavior-Driven Development (which we will now refer to as "#BDD") follows on from the ideas and principles introduced in #Test-Driven Development. The key points of writing tests before code really apply to BDD as well. The idea is to not only test your code at the granular level with unit tests, but also test your application end to end, using acceptance tests. We will introduce this style of testing with the use of the Lettuce testing framework.
http://pythonhosted.org/behave/
behave is behaviour-driven development, Python style.
Behavior-driven development (or #BDD) is an agile software development technique that encourages collaboration between developers, #QA and non-technical or business participants in a software project. We have a page further describing this philosophy.
behave uses tests written in a natural language style, backed up by Python code.
Once you’ve installed behave, we recommend reading the
tutorial first and then
feature test setup,
behave API and
related software (things that you can combine with behave)
finally: how to use and configure the behave tool.
https://pypi.python.org/pypi/pytest-bdd
#BDD library for the py.test runner
#pytest-bdd implements a subset of Gherkin language for the automation of the project requirements testing and easier behavioral driven development.
Unlike many other BDD tools it doesn’t require a separate runner and benefits from the power and flexibility of the #pytest. It allows to unify your unit and functional #tests, easier continuous integration server configuration and maximal reuse of the tests setup.
Pytest fixtures written for the #unit_test s can be reused for the setup and actions mentioned in the feature steps with dependency injection, which allows a true BDD just-enough specification of the requirements without maintaining any context object containing the side effects of the Gherkin. imperative declarations.