Blogposts, discussions, eventsTest automation tipWhen doing API testing, there are many things we might want to test. For example, in this test, we're making sure that the name returns unaltered from the server. But what about the other keys? We need to take a look at the response and take a look at the response body. This is not really a problem, but it may become one when we are dealing with hundreds of tests. And this is where TypeScript becomes incredibly useful. We can create an interface that will define the board body response. What we can do is we can tell the request function to expect board to be a return type. When we now start typing expect function, the board body will start auto-completing types from our board. 1 interface Board { 2 name: string 3 user: number 4 starred: boolean 5 created: string 6 id: number 7 } 1 cy.request<Board>('/api/boards').then(board => { 2 expect(board.body.name).to.eq('new board') 3 }) Meme of the week
|
|
Sign up for weekly tips on testing, development, and everything related. Unsubscribe anytime you feel like you had enough 😊
Hey Reader, It’s been a while since I’ve issued a newsletter, but I’m hoping to get back on track. There are just so many interesting things happening in the world of IT that I want to share with you all. But I’ve decided to change my approach to writing this newsletter a little bit. In the past, my main goal was to come up with some idea or some thought and basically write a post. This put a lot of pressure on me and I never wanted to force myself into writing a newsletter when I had nothing...
Filip Hric 22th July 2025 AI, BDD, and Why We're Bad at Predicting the Future Hello Reader,Lately, it seems the conversation around AI has shifted. We're moving past the initial "what can this chat window do?" phase and into the more practical, and sometimes awkward, integration into our development lifecycle. To me, one of the most interesting moments recently is that we're seeing major players like Amazon use BDD for AI-driven requirement planning. Plus the whole ecosystem of AI builder...
Filip Hric 13th May 2025 TO BE OR NOT TO BE (TECHNICAL) Hey Reader!There’s an ongoing debate in the QA world on whether it makes sense to get technical or not. I remember having a fairly heated debate on this last November at Agile Testing Days in Potsdam. My talk titled "Test like a developer, develop like a tester" argued that we should put the effort as testers to become experts in the software we test. And yes, that includes having a fair bit of developer knowledge. Jason Arbon called...