5 Reasons You Should Care About Code Coverage
source
Code coverage is an important aspect of good engineering practice. Without it, you are flying a bit blind writing tests.
Weekly newsletter about leadership, technology, books and anything else we felt compelled to share with others
source
Code coverage is an important aspect of good engineering practice. Without it, you are flying a bit blind writing tests.
Setting up test cases for code that manage data can be challenging but it's an important skill to reliably test your code. You might have heard of the setup and teardown methods in unittest. In pytest you use fixtures and as you will discover in this article they are actually not that hard to set up. Fixtures have been labelled pytest's killer feature so let's explore them in this article using a practical example.
source
We're several months into the work at the firm, and one very interesting concept has come to the fore: The implementation of preemptive change is about desire. Or, as one senior leader proffered at a recent executive steering committee meeting, "Ya' gotta wanna do it." I love this statement: "Ya' gotta wanna do it!" It's a straightforward way to summarize an otherwise elegant management philosophy -- one that connotes desire, focus, and a commitment to change. In the interest of furthering this theory, let me propose five basic leadership principles we can use to form the backbone of the "Ya' gotta wanna do it" philosophy.
source
The modern iterative software development lifecycle has developers checking in code to version control systems frequently, with continuous integration handling building and running automated tests at an almost equally fast rate. This can generate an enormous amount of test data. Here’s how you can ensure you are reporting results effectively across your team and realizing all the benefits of that information.
source
A good software architecture allows decisions about frameworks, databases, web-servers, and other environmental issues and tools, to be deferred and delayed. A good architecture makes it unnecessary to decide on Rails, or Spring, or Hibernate, or Tomcat or MySql, until much later in the project. A good architecture makes it easy to change your mind about those decisions too. A good architecture emphasizes the use-cases and decouples them from peripheral concerns.
source