Navdeep Kumar

Testing documentation is important. But do you know why? Without thorough test documentation, it's challenging to maintain continuity, consistency, and communication in software development projects. Read our latest article to learn why comprehensive test docs are key and how to establish them for your software testing efforts: https://hubs.li/Q02TW-r70

3

🌍 The Growing Demand for Software Testers in the UK The tech landscape in the UK is rapidly evolving, and with that comes an increased emphasis on delivering high-quality, reliable software. This surge has fueled an unprecedented demand for skilled software testers who ensure that applications not only function but excel in meeting user expectations. Our latest blog dives into the reasons behind this demand, exploring how shifts in technology, user expectations, and agile methodologies have placed software testing at the heart of software development. 🔍 Key Takeaways: Why companies are doubling down on QA as a strategic investment. The skills that make a software tester stand out in the UK market. Trends shaping the future of software testing. Want to know what makes the UK a hotspot for talented software testers and how this impacts the tech industry at large? Read more here: https://lnkd.in/gCXvVZdG #ContextQA #SoftwareTesting #QAJobs #TechIndustry #UK

3

Beware of Template-Driven Development (TDD... but not the one you think!) Templates can be a lifesaver in development, but there's a big trap many teams fall into—using them without truly understanding their purpose. Whether it's BDD's Given-When-Then, story mapping, or the classic "As a user... so that" format, these tools are meant to guide, not to be followed blindly. When teams overlook the intent behind templates, they end up with fragile processes, unclear business goals, and lots of headaches later. Use templates wisely. Don’t let them use you. #AgileDevelopment #BDD #SoftwareTesting #TestAutomation #AgileTesting #AutomationTesting

3

After the establishment of the Software Testing Alliance, Armoury+ introduced project management and web automation functionalities in one go. This article provides a comprehensive introduction to the six major systems currently included in Armoury+ and explains why software testing teams need their own project management system. The API monitoring feature is a bit of a teaser, as it will allow, by the second half of this year, for scattered APIs to be more precisely grouped into a single monitor, which will check for any errors. From a corporate perspective, the responsibility for API monitoring might typically fall under SRE, IT, or backend development, but now, software testing teams can easily handle it as well.

2

Struggling with test maintenance? We get it— 1. navigating flaky tests,   2. badly written tests,   3. growing technical debt,   4. changes in test environments,   5. resource constraints,   6. lack of strategy around test automation, and   7. evolving application interfaces can feel like an uphill battle! Our blog post walks you through these challenges and provides practical tips to keep your tests accurate and effective. Take a read and simplify your testing strategy: https://lnkd.in/gDutj_aF #testmaintenance #softwaretesting

20

💡Why Test Scripts Break? Think of your test scripts as the guardians of software quality. They ensure everything runs smoothly, but just like any good guardian, they need constant attention. Here’s why your scripts break: 🔸Software Updates and New Features: Every new feature or update means there’s a chance your scripts need tweaking to reflect the changes. 🔸UI Changes and Element Modifications: Did the design team revamp the login screen? Uh oh, script updates are afoot! 🔸Bug Fixes and Code Refactoring: Even bug fixes and code cleanups can sometimes break your scripts, requiring adjustments to keep them working as intended. The problem is, manually updating scripts for every single change is a time-consuming and tedious task. It takes away valuable time you could be spending on more strategic testing activities. Read the full blog about Test Script Maintenance and solution here: https://lnkd.in/g5Xs9rp3 #AI #SoftwareTesting #TestAutomation #QualityAssurance #Webomates #WeboAI #DigitalTransformation

4

What does scrum have to do with customer onboarding? Quite a bit, says Jasmine Reynolds. Jasmine will be speaking at Propel24, where she will share how scrum methods can be used to enable quick, seamless onboarding experiences. It's virtual, and it's free 🚀 Register here: https://lnkd.in/dQh3S6QY #CustomerOnboarding #Propel24 #ProfessionalServices #Rocketlane

2

Episode 2 Now Live - “From a testing perspective, we can actually look into what we can contribute.” – Iris Pinkster O'Riordain In the latest episode of the EuroSTAR Community Podcast, Iris and Russell discuss sustainable testing practices and the need for efficiency. How can testers make mindful choices to reduce their environmental impact? 🎙️ Listen Here: https://lnkd.in/etEAJi9i #EuroSTARCommunityPodcast #SustainableTesting #SoftwareTesting

1

Complete test coverage is unattainable. CQE can help you understand how the Business Impact × Technical Complexity (BI × TC) ratio offers a practical framework for optimising the allocation of software testing budgets. Get in touch for more information, and to discuss how we can help you implement a framework to enhance your test coverage. #SoftwareTestingBudget #BusinessImpactTechnicalComplexity #CQEServices

8

Should all your BDD scenarios be UI end-to-end tests? 🤔 It’s a common misconception, especially with the popularity of tools like Selenium or Cypress. But here’s the truth: Your BDD scenarios should be written at the "lowest responsible level"—the lowest level where you can confidently verify functionality. This could be at the UI, API, or even the unit test level. BDD isn’t tied to a specific layer of testing. It’s about crafting scenarios that are implementation-neutral, allowing you to decide the most efficient level to test. Don’t lock yourself into UI tests unnecessarily. Focus on where you can get the most value, and your testing strategy will thank you. #BDD #SoftwareTesting #AgileTesting #TestAutomation #SerenityBDD #ContinuousTesting #DevOps #QualityAssurance #Cucumber #Selenium

9

Both 'early Model Based Testing' (eMBT) and Behaviour Driven Development’ (BDD), emphasizes collaboration between developers, testers, and business stakeholders by focussing on creating a common language that is easily understood by everyone involved, leading to a deep shared understanding. To achieve this in the BDD approach, a requirements discovery practice such as 'Feature mapping' or 'Example mapping' is often used. 💡 But did you know that in TestCompass it is possible to execute these collaborative requirements discovery practices. And after that you can easily convert the 'Feature map' or 'Example map' into a graphical model and automatically generate the minimum set coverage based Gherkin .feature files. Curious how this works in practice and what its benefits are? Read our blog "BDD requirements discovery practices supported by TestCompass 👇 https://lnkd.in/eCN8_rxy #bdd #MBT #eMBT #collaboration #communication #sharedunderstanding #easytouse #Gherkin #featurefile #scenarios #featuremapping #examplemapping #conversation #requirements #discovery #formulation #3amigos

9

Both 'early Model Based Testing' (eMBT) and Behaviour Driven Development’ (BDD), emphasizes collaboration between developers, testers, and business stakeholders by focussing on creating a common language that is easily understood by everyone involved, leading to a deep shared understanding. To achieve this in the BDD approach, a requirements discovery practice such as 'Feature mapping' or 'Example mapping' is often used. 💡 Did you know that in TestCompass it is possible to execute these collaborative requirements discovery practices. And after that you can easily convert the 'Feature map' or 'Example map' into a graphical, readable model and automatically generate the minimum set of coverage based Gherkin .feature files. Curious how this works in practice and what its benefits are? Read our blog "BDD requirements discovery practices supported by TestCompass 👇 https://lnkd.in/eCN8_rxy #bdd #MBT #eMBT #collaboration #communication #sharedunderstanding #easytouse #Gherkin #featurefile #scenarios #featuremapping #examplemapping #conversation #requirements #discovery #formulation #3amigos

9

What challenges are you currently facing? Struggling with a particular Scrum event? Wanting to know more about implementing Continuous Improvement practices? The Agile O Group Virtual Coffee Chat is the ideal place to come and discuss these. Check out our revamped Miro board designed by Wayne Smallman / MilScrum 📅 May 9th ⌚ 1230 - 1330 Register in the Agile O Group Community of Practice. (link below) #collaboration #teamwork #community #agile

3

5 Comments

Keeping Test Automation Code Simple & Reliable The biggest challenge with test automation? It’s easy to let complexity creep in, leading to fragile, hard-to-maintain scripts. But here’s the thing: simplicity isn’t about skimping on testing, especially when dealing with complex business logic. It’s about building sustainable, robust tests that don’t break at every turn. Here’s how: 1️⃣ Break Down Complexity: Focus on individual components, edge cases, and specific business rules rather than all-in-one end-to-end tests. 2️⃣ Bake in Testability Early: Collaborate with your team before coding begins—design with testability in mind. Discuss hooks, APIs, data needs, and anything to make testing more seamless. 3️⃣ Prioritize Reliability Over Complexity: Simple, well-defined tests offer reliability you can trust. By addressing testability upfront, you create a test suite that’s dependable, maintainable, and ready for the long haul. #TestAutomation #QualityAssurance #SoftwareTesting #AutomationTesting #AutomationSkills #AgileTesting #DevOps #AutomationTips #TestingStrategy #AgileAutomation #AutomationStrategy #TestCases #AdvanceTesting #TestingCareer #AiTesting #SoftwareTester #TestingJobs 

6

Episode 115 is live and the peers talk about the trend of no testers in teams? Is it still a thing? Or are we starting to go full circle? Chris Armstrong and Russell Craxford are joined by Callum Akehurst-Ryan and first time host Leigh Rathbone. Has the perception of what testing is, changed? What are your thoughts on teams with no testers? And more importantly, what is your favourite fictional AI? https://lnkd.in/ekP9p4Uw

12

1 Comment