Venushka Perera

Should be an interesting and insightful talk and discussion.

4

Karl Scotland is one of the smartest people out there on lean/kanban/agile software planning and development processes. While #DevOps dominates the conversation in this space, it's important to remember that the 1st of the 3-ways of DevOps is "flow". These rules are the key to achieving flow.

6

In this article, describing an approach to writing tests with a clear division into separate stages, each performing its specific role. This facilitates the creation of tests that are easier to read, understand, and maintain. Read more about arranging HTTP request testing in Spring: https://lnkd.in/ed8dAbeX

1

Since the introduction of the Delivery API in Umbraco 12, the amazing Umbraco community has been asking a bunch of questions on how to do this and that with the API. A lot of those questions have led to a better API feature set and/or improved documentation 🚀 A few have not (yet) made it into the official docs. I have put together a blog post describing some of the most interesting/useful, undocumented extension points in the Delivery API. 👉 https://lnkd.in/dNRVh3hn #umbraco #headless

29

2 Comments

💡React Performance Improvement Tip💡 As you might know, whenever a parent component is re-rendered due to state change, all of its child components also get re-rendered. But If you have some heavy component that does not depend on any state or prop then you can pass it as a children prop. And data passed as a part of children prop will not be re-rendered again even if the parent component is re-rendered. Take a look at the below code: function Child() { console.log('rendered'); return ( <ul> {[...Array(1000).keys()].map((number) => ( <li key={number}>{number + 1}</li> ))} </ul> ); } function Parent() { const [counter, setCounter] = useState(0); return ( <> <p>Counter: {counter}</p> <button onClick={() => setCounter((counter) => counter + 1)}> Increment </button> <Child /> </> ); } function App() { return ( <div className='App'> <Parent /> </div> ); } In the above code, as we're rendering the Child component inside the Parent component, code from the Child component will be executed on every click of the increment button because the Parent component is re-rendered. But If you pass that Child component as a children prop to the Parent component, then it will not be re-rendered again even if the Parent component gets re-rendered as shown below: function Child() { console.log('rendered'); return ( <ul> {[...Array(1000).keys()].map((number) => ( <li key={number}>{number + 1}</li> ))} </ul> ); } function Parent({ children }) { const [counter, setCounter] = useState(0); return ( <> <p>Counter: {counter}</p> <button onClick={() => setCounter((counter) => counter + 1)}> Increment </button> {children} </> ); } function App() { return ( <div className='App'> <Parent> <Child /> {/* this Child component will go as a children prop */ } </Parent> </div> ); } This is one of the simple and easiest way to improve performance of your React application. 𝗖𝗵𝗲𝗰𝗸 𝗼𝘂𝘁 𝘁𝗵𝗲 𝗖𝗼𝗱𝗲𝗦𝗮𝗻𝗱𝗯𝗼𝘅 𝗱𝗲𝗺𝗼 𝗹𝗶𝗻𝗸𝘀 𝗶𝗻 𝘁𝗵𝗲 𝗰𝗼𝗺𝗺𝗲𝗻𝘁 𝘁𝗼 𝘀𝗲𝗲 𝗶𝘁 𝗶𝗻 𝗮𝗰𝘁𝗶𝗼𝗻. 𝗙𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝘂𝘀𝗲𝗳𝘂𝗹 𝗰𝗼𝗻𝘁𝗲𝗻𝘁, 𝗱𝗼𝗻'𝘁 𝗳𝗼𝗿𝗴𝗲𝘁 𝘁𝗼 𝗳𝗼𝗹𝗹𝗼𝘄 𝗺𝗲. #javascript #reactjs #webdevelopment

45

5 Comments

Interesting paper about property based testing in real usage. Looks like as with any written tests it can help devs have clarity on their solution specs and helps document code. Harder to implement but more valuable when in place. https://lnkd.in/g_UEJvXW

5

Howdy folks, I've written an article about a testing framework called Playwright. It's a concise and practical summary of what the framework has to offer with examples (and even a dubious analogy involving cake), what more could you want? https://lnkd.in/eKXEN6xN

12

5 Comments

It's time for one of my classic "I told you so" moments. This article is talking about why organisations are stepping back from scrum masters https://lnkd.in/eWwx8eQn. Here is something I wrote in 2015 explaining why this is happening https://lnkd.in/e7XffFxB

3

Successful Test Engineering and The ISTQB Programme for Professional Capability Development | The Agile Stream The Agile stream contains only 3 units, but collectively they serve to fulfil the needs of foundation level agile testing through to the differing roles and aspects of a large, distributed agile project. Building on the principles taught at Foundation Level, the stream contains: • Agile Tester, which must be passed before venturing in the either of the higher-level certifications within the stream. Note: Holders of an IISTQB Foundation certificate at Version 4 or later need not obtain an Agile Tester certification before embarking on the other certifications in this stream. • Agile Technical Tester for those wishing to progress on a technical route, rather than management of larger agile projects. Read More Here 👉 👉 👉  https://lnkd.in/edBRTCFJ  #agile #scrum #scrummaster #agilecoach #projectmanagement #productowner #management #kanban #innovation #agiledevelopment #business #agilemethodology #agiletransformation #productmanagement #leadership #agileleadership #training #agilecoaching #agility #designthinking #lean #technology #agiletraining #businessanalyst #digitaltransformation #pmp #agilemindset #businessagility #devops 

1

This is a good article on the Shift left approach for developers.

4

1 Comment

Stop calling automated testing 'checking'. One of the things you will have heard as a QA engineer is that 'automated tests don’t test'. The idea behind this is a bit nebulous to me, to be honest, but clearly, it has to do with the assumption that no new information can be gained from running an automated test script. In this school of thought, we’re told that only active human intervention gains this new information. I’ve forever been baffled by this. Automated tests are created by humans, who (hopefully!) think about what risk they are covering, and why we need the information this test provides us with. Because knowing that your signup flow is functional isn’t more or less relevant whether a human checks it or a machine does.

114

73 Comments

I think I may be a little late to the party here but, blimey Charlie testcontainers.com is super useful for your integration tests. 1) I can see why Docker snapped up the developers, AtomicJar 2) testcontainers.com may make building integration tests just a little too easy

6

An important read, and a topic near and dear to me.

3

1 Comment

Excellent read on how to organize #EndToEnd Tests using #playwright... https://lnkd.in/e4VniVtU

1

I'd like to extend my heartfelt thanks to my mentor James Gray for his exceptional coding coaching sessions. Dedicating an extra four hours, James provided additional classes that was not only informative but truly eye-opening. The practical examples he shared during the classes have significantly boosted my confidence in no-code, low-code, and pro-code AI development. It's mentors like James who make the learning fun. #AIdevelopment #ProfessionalGrowth

16

1 Comment

I'm observing a team writing code as an ensemble without TDD. I am selfishly delighted in the confirmation of how valuable TDD is to me as I use it. The team is implementing a new function that's doing list of list manipulation and returning something. They are all over the place with naming things, creating objects, streaming, mapping, flattening maps, return object, variables, naming...so many squirrels. Too many squirrels to even really focus on "what's the simplest first thing we could do?" TDD is so much more than writing a test first. It's a framework that helps me focus, prioritize, structure, and order my thoughts. Test Driven Development is an immensely helpful design and focus tool. I should also note, that I am beginning of working with this team and meeting them where they are. #codelife #devlife #TDD #testdrivendevelopment #unittesting #designthinking #problemsolving #structuredthinking #focus #mindset #toomanysquirrels #codingchaos

282

62 Comments

The question about “how to make sure the architecture is testable” stuck in my head when discussing software architecture 3 weeks ago on 'This week in testing' by Ministry of Testing I suggested M.U.S.T.A.P.O as part of the discussion, because testing is not just a stage . I discussed the benefit of testability as a consideration when looking at the architecture. How it relates to 'shifting left', but also 'shifting right'. Which is why this mnemonic is so apt. Every step involves testing and Quality. https:l/https://lnkd.in/ewuMcEHj -quality-in-software-88c25f812258?source= friends_link&sk= ff27e1175c84e8a7b97a0942141a82b6 I explain M.U.S.T.A.P.O. here in Medium.

38

6 Comments

I don't often post things like this but I'm seeing a lot of misinformation around TDD and it not working or is a failure. I've been responsible for implementing or pushing TDD for over 15 years now and have gone through various different frameworks, and methods. When I joined SRL there was a growing bug problem, and zero worth unit, integration, or UI tests. Over the last three years Martin Thorne, Steve Pugh, Olufemi Adesina, Kathryn Beggs, and latest recruit Maude Williamson have worked diligently to create Unit, Integration and Cypress UI frameworks in place. The coverage for each is on average over 80% and continues to improve. It is the responsibility of developers to test their own code and is often the first line of defence against poor requirements. We're now averaging +1 bug/month reported from clients, and usually these are P3, P4s, or disguised scope creep. Simply put TDD DOES work - but as with any skill if you've not got genuinely experienced people then it's going to be a mess. *Ahem* Agile my eyes are on you.

18

1 Comment