Tech Insights

<p>pytest makes it easier to flag tests that are expected to fail. It's really useful when in development, e.g., feature not yet implement or bug not totally fixed. Making use of it is as simple as:</p> <pre><code>import pytest @pytest.mark.xfail def test_xpto(): ... </code></pre> <p>This way, it'll be presented differently in the terminal report and one can track whether a test is failing as expected or unexpectedly passing.</p> <p>While the test marked as expected to fail will be presented as <code>xfailed</code> in the test summary, if it passes it'll be displayed as <code>xpassed</code> and when that happens it's not displayed as <code>passed</code> because that test was marked to expect failure.</p> <p>One can even go further and set a reason to why a test is expected to fail, one can set a reason:</p> <pre><code>import pytest @pytest.mark.xfail(reason="feature not totally implemented") def test_xpto(): ... </code></pre> <p>To display this reason in the test summary, one can use the <code>-r</code> option with the corresponding "short" letters shown in progress(<code>x</code> for <code>xfail</code> and/or <code>X</code> for <code>xpass</code>), e.g. <code>pytest -rxX</code>.</p> <p>For more information, check the documentation at: #xfail-mark-test-functions-as-expected-to-fail</p>

<p>New browser features to secure Single Page Applications: </p>

<p>The importance of Design QA in digital product design </p>

<p>sketching on whiteboards and sticking post-its on walls can do a lot for a product team </p>

<p>If you want to add a unique non-nullable field to a table with existent rows, you'll need to a few extra steps because <strong>Django generates the value to populate existent rows only once</strong>. For the extra steps, check these instructions in #migrations-that-add-unique-fields</p>

<p>Nice tip if you want to add keys to objects conditionally </p>

<p>How to use microinteractions to improve UX design </p>

<p>If you using modals on your react application you have to check react-portals Portals make your react components to be rendered outside the parent component (eg.: append to body)</p>

<p>how to write good error messages </p>

<p>the pros &amp; cons of group chat, and how to make the best use of it </p>

<p>A case against presence status in online work tools </p>

<p>Roadmap to becoming a React developer in 2018: </p>

<p>What Is The Best Screen Size to Design Websites in 2018 </p>

<p>How bidirectional scrolling can save responsive design </p>

<p>Using Paramiko through their docs' examples might look complicated, but here's a simple 5 liner that works </p>

<p>Metrics versus experience </p>

<p>how to think about design systems </p>

<p>how to do an UI inventory [design system, UI</p>

<p>Write Dumb Code </p>

<p>How does Redux work? </p>

<p>Raising a Design System in a team </p>

<p>Aligning SVG icons to text </p>

<p>how to integrate design into the agile process </p>

<p>What are JavaScript promises? </p>