The latest articles on DEV Community by tatiana-sh (@tatianash). https://dev.to/tatianash https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F32209%2Fa3e6e848-cae1-47e0-af20-f7dfa282eca3.png https://dev.to/tatianash en tatiana-sh Mon, 18 Sep 2017 11:14:53 +0000 https://dev.to/tatianash/how-the-definition-of-quality-evolves-with-a-project https://dev.to/tatianash/how-the-definition-of-quality-evolves-with-a-project <p>What is quality? There are multiple definitions. In general, it is a level of satisfaction by conformance to expectations, both implicit and explicit, by all stakeholders. </p> <p>It is a common thing that a lot of changes are introduced during the project development. New requirements are uncovered, both functional (new features) and non-functional (e.g. accessibility, performance or localization requirements).</p> <p>Later, as the project evolves, the project goals may change. The basic test strategy and approach <a href="https://binary-studio.com/2017/09/14/definition-quality-evolves-project/">should be updated along with the project evolution</a>.</p> testing codequality tatiana-sh Fri, 08 Sep 2017 09:46:35 +0000 https://dev.to/tatianash/how-to-prioritize-your-bug-fixes https://dev.to/tatianash/how-to-prioritize-your-bug-fixes <p>Any bug is a headache. </p> <p>On the one hand, bug fixing is expensive in terms of both time and money. It takes resources and time that could be allocated to new feature development, pushing your project back. </p> <p>On the other hand, not fixing bugs is risky for the development process, business and even for end-users’ lives in some cases. It creates obstacles and technical debt. It makes users unhappy and leads to costly outcomes in fulfilling the business need. </p> <p>So what is the proper solution? The trick is in fixing the right stuff. You should balance between bug fixing and implementing new requirements by <a href="https://binary-studio.com/2017/09/07/prioritize-bug-fixes/" rel="noopener noreferrer">prioritizing your bug fixes</a> properly.</p> testing codequality bugs tatiana-sh Mon, 04 Sep 2017 10:53:34 +0000 https://dev.to/tatianash/minor-bugs-and-how-to-define-your-own-strategy-of-dealing-with-them https://dev.to/tatianash/minor-bugs-and-how-to-define-your-own-strategy-of-dealing-with-them <p>One of the questions many teams encounter is what they should do with all those minor bugs found in the product, especially given budget limitations.<br> We definitely should fix minor bugs as soon as possible, but usually during the earlier stages of the project it’s more valuable for business to be responsive to the changing market and find its audience than fixing all minor bugs. Remember Facebook’s old “Move fast and break things motto, for instance.<br> We can’t fix every single minor bug we find, that’s a common sense. But we can’t ignore them either, otherwise they will pile up and eventually will cause harm to business.<br> If you already have quite a list of minor bugs in your bug tracker, don’t hesitate to <a href="https://binary-studio.com/2017/08/04/dealing-minor-bugs/">define your own strategy of dealing with them</a>.</p> codequality testing bugs