ãã¦ãpython3.4ã¨ã trove ã«ãç»é²ãããããèªåã§æ¸ãã¦ãã©ã¤ãã©ãªã¯å¯¾å¿ããã¦ããããªã¨ããã¨ããã§ãã ã§ãå種ãã¼ã¸ã§ã³ã§ã®ãã¹ããéãã®ã« tox 使ãã®ãæè¿ã®å¸¸èã«ãªã£ã¦ãã¦ããã¨æãã¾ãããtravisã§ciããããã¨ããã¨ã.travis.ymlã«åããããªãã¨ãæ¸ãã¦ãã¾ãããã§ãã ããã«ãä»ã®ã¨ãã travis ã§ã¯python3.4ãå ¥ã£ã¦ããªãã æè¿æ³¨ç®ãã¦ãã次æPyPIã®å®è£ ã§ãã warehouse ãã¿ã¦ããããpython3.4ã§travisã§ã®ãã¹ããå®è¡ããã¦ããã ããããä¸ã§toxãå¼ã¶ããã«ãã¦ããã python3.4ã¯åã«deadsnakesããapt-getã§ã¤ã³ã¹ãã¼ã«ãã¦ããã ãã§ãã toxå¼ã¶ãã¨èªä½ã¯ç°¡åã§ãåã« .travis.yml 㧠script ã« tox ãæå®ããã°OKã ãã ããããã 㨠to
Work with virtual environments¶ We recommend to use virtualenv environments and use pip (or easy_install) for installing your application and any dependencies as well as the pytest package itself. This way you will get an isolated and reproducible environment. Given you have installed virtualenv and execute it from the command line, here is an example session for unix or windows: virtualenv . # cr
Being a fan of good testing, I'm always trying to find ways to improve testing on various projects. Travis CI and Coveralls are really nice ways to set up continuous integration for your open-source projects. A couple months ago I finally started hearing grumblings about tox and how everyone was it using for their Python test automation. Every time I'd try to wrap my head around it, something alwa
ã©ã³ãã³ã°
ãç¥ãã
ã©ã³ãã³ã°
ãªãªã¼ã¹ãé害æ å ±ãªã©ã®ãµã¼ãã¹ã®ãç¥ãã
ææ°ã®äººæ°ã¨ã³ããªã¼ã®é ä¿¡
å¦çãå®è¡ä¸ã§ã
j次ã®ããã¯ãã¼ã¯
kåã®ããã¯ãã¼ã¯
lãã¨ã§èªã
eã³ã¡ã³ãä¸è¦§ãéã
oãã¼ã¸ãéã
{{#tags}}- {{label}}
{{/tags}}