• Five for Friday – September 24

  Back for another week of random links and interesting articles from the internet. For the ‘murican readers here, the US Vaccine Tracker is a nice look at vaccine rates across a variety of demographics.A great article on metrics that don’t suck from Greg PacigaJust this week, I was in a conversation about automating development environment setups…and then I also run into this article on the subject (and a pointer to gitpod).It’s been a while since I’ve pointed to the Netflix Tech blog, but there’s a nice article on A/B testing (with the slash) this week.Finally – I found this article on how the new generation of college students thinks about files and folders fascinating. If you’re my age, you may find it interesting too. See you next week.

  24.09.2021 | 12:15 קרא עוד...

• Cypress Tutorial | How To Organize Cypress Test

  In this Cypress tutorial we are going to talk about test structure, how to organize cypress tests. Let’s open a new blank test file exampleTest.spec.js In each spec file, you should start with set in the first row the reference command /// <reference types="cypress" /> This command will give your cypress test autocomplete power and will help you to code faster. Mocha Mocha is a feature-rich JavaScript test framework running on Node.js and in the browser, making asynchronous testing simple and fun.Mocha tests run serially, allowing for flexible and accurate reporting while mapping uncaught exceptions to the correct test cases. Mocha, provides describe(), context(), it() and specify() blocks.context() is identical to describe() and specify() is identical to it(), so choose whatever works best for you. I work with the describe() and it(). Describe() Block In the describe() you provide the general description of what your test will be about.Then you open a callback function with curly braces and this will create the body when you will insert the tests. describe('this is a describe block', () => { }) Create it() block inside the describe, this block is the test case where you type the actual test code.In the result, you will see that the test case demo was executed and the name of the test was test case demo. describe('this is a describe block', () => { it('test case demo', () => { }); }) This is the most simple structure, how the test should be organized inside the spec file.You can put as many tests as you want inside the describe block. describe('this is a[…]

  24.09.2021 | 11:44 קרא עוד...

• Is it possible to improve the impact of our Testing by simplifying it?

  I admire the simplicity of TDD. Red, Green, Refactor. Write a test, see it fail. Write some code, see the test pass. Refactor your code, the test should still be green. It’s simple to describe and a simple concept to understand. Except it’s not simple. I rarely practice TDD by myself these days, but I clearly remember how hard it was first picking it up. It took a lot of frustration and failure to get to a point where I felt comfortable. Compare that to Testing. Testing is hard, just like TDD. Testing also feels hard to understand. There’s Strategies, Plans, Frameworks, not to mention the nebulous nature of knowing what and what not to test. You might’ve worked with a great software tester. As with all experts, great practitioners will make things look and feel simple, but they will all tell you that it’s not. For a long time I’ve been thinking about how I could simplify my testing world. To make it easier for me to hone my own craft and if possible, help those I work with get over that initial barrier. This is where I’ve got to. Explore, Act, Improve. Explore ‘something’ to gain knowledge. Use the knowledge to act. Improve how we explore. The current working title for this process is Action Driver Exploration. Better suggestions are very welcome! Déjà vu As with all things, nothing is truly new. As I’ve gone through my career I’ve reached points I might classify as step-changes in my[…]

  24.09.2021 | 11:03 קרא עוד...

לרשימה המלאה >>