testandcode's profile picture. Test & Code Podcast. Hosted by @brianokken

Test & Code

@testandcode

Test & Code Podcast. Hosted by @brianokken

184: Twisted and Testing Event Driven / Asynchronous Applications - ⁦@glyphtestandcode.com/184


Test & Code 님이 재게시함

“Don’t use pytest-black”. That’s ok for most pythonistas. But... the use case I ❤️ for all the bridging plugins is the scientist/engineer new to Python. I can tell them “Just run pytest” and it runs black, flake8, flake8-isort and my favorite... flake8-docstrings. It’s scales me.


Test & Code 149

이 트윗은 더 이상 사용할 수 없습니다.

Test & Code 144: TDD in Science testandcode.com/144 Testing is essential to have trusted software. We want to trust science, so we need to trust the software used in research. However, testing is still a challenge in science. Join the discussion.

pythontest.com

PythonTest

Brian Okken's blog + links to pytest books, courses, and podcasts


Test & Code 107: Property Based Testing in Python with Hypothesis - @ahultner testandcode.com/107 Hypothesis combines human understanding of your problem domain with machine intelligence to improve the quality of your testing process while spending less time writing tests.


Test & Code 102: Testing REST APIs, minimizing mocks, London vs Detroit, and even Architecture Patterns in Python on this weeks Test & Code, with Harry Percival testandcode.com/102


Test & Code 94: The real 11 reasons I don't hire you - Charity Majors, @mipsytipsy


Episode 93

이 트윗은 더 이상 사용할 수 없습니다.

Test & Code 님이 재게시함

@testandcode Loved that latest episode on parameterization. Made me miss working with Python/pytest day-to-day so much.


Test & Code 님이 재게시함

"Programming was like a box with unlimited legos" is a fantastic way to describe the first wonder of code (via @traskjd on @testandcode 88)


Test & Code 님이 재게시함

Error monitoring. Crash reporting. Performance monitoring. You keep running into these terms, but what do they actually mean? And how can they impact your business? Join Raygun CEO @traskjd as he deciphers modern-day monitoring over on @testandcode: buff.ly/2nHS0cF ⚡️

raygunio's tweet image. Error monitoring. Crash reporting. Performance monitoring. You keep running into these terms, but what do they actually mean? And how can they impact your business? Join Raygun CEO @traskjd as he deciphers modern-day monitoring over on @testandcode: buff.ly/2nHS0cF ⚡️

Test & Code 83: PyBites Code Challenges behind the scenes - with Bob Belderbos ⁦@bbelderbostestandcode.com/83


pytest features since 3.0 that you should know about. @codewithanthony is a core pytest contributor and joins Brian on this weeks Test & Code testandcode.com/82


Test & Code 81: TDD with flit testandcode.com/81 This episode discusses editable installs with flit, a good TDD editor layout, test case grouping, batching tests to reduce context switch time, and even utilizing git tags.


Test & Code 님이 재게시함

Day 51 of #100DaysOfCode #python Two @pybites exercises: 1. Complete a User class: properties and representation dunder methods. 2. Simple length converter (convert in to cm and the opposite). Been starting to use PyCharm Pro which I got 4 months for free via @testandcode.


Test & Code 님이 재게시함

Today I continued working on the C++ course and listened to the @testandcode podcasts that I fell behind on. #100DaysOfGameDev #R1D41


46: Testing Hard To Test Applications, with @anthonypjshaw testandcode.com/46


Test & Code 님이 재게시함

We just added @testandcode to our Podcast feeds - ministryoftesting.com/feeds/podcasts


Test & Code 님이 재게시함

Check out this 8-minute @testandcode podcast episode on preparing for technical presentations with @kelseyhightower - it's full of practical tips buff.ly/2ut8PZr

techloop_io's tweet image. Check out this 8-minute @testandcode podcast episode on preparing for technical presentations with @kelseyhightower - it's full of practical tips buff.ly/2ut8PZr

Test & Code 님이 재게시함

Transcript up for “41: Testing in DevOps and Agile”. testandcode.com/41 Nicely formatted version sent to Patreon supporters.


Loading...

Something went wrong.


Something went wrong.