Amit Vaidya

Tired of the pre-launch chaos? As a developer myself, I get it! My team and I built a solution to make testing smarter, not harder. Get ready to say goodbye to testing headaches with AutoFlow Studio! Missed out on early access to AutoFlow Studio? Your chance is here! The next round is opening soon... #testing #automation #ai #qa #uitesting

18

I've just begun delving into Playwright for UI automation, and I'm truly amazed by its capabilities. What sets Playwright apart from Selenium, in my opinion, is its exceptional reliability in testing. With significantly fewer flaky tests, it alleviates a major headache often encountered when running extensive regression test suites. Moreover, its wait mechanism and ability to seamlessly scroll to elements not immediately visible on the page add to its reliability and usability. If you are also looking to learn automation or plan to move from manual to automation, I can guide you through this transition. Book my 1:1 session through Topmate https://lnkd.in/grASjcik Here is the link to my youtube channel : https://lnkd.in/gVqq-gqH #playwright #selenium #automation #sdet #topmate #careerguidance #qaautomation #manual #testframework #typescript #youtube #careerbreak #mentalhealth

20

When I started testing, I was often asked to write a test plan for . Or, sometimes, I’d be handed a 50 pager with the ask to “review the test plan”. These plans commonly detailed things like environment setup, OS, test steps, and other minutiae of how exactly the testing of was to be executed. These days, I much prefer to write test strategies - instead of detailing every step, which inevitably leads to a lot of rework throughout the development process, we think strategically about how we can test certain aspects of our application, what kind of tests we’ll need and if those can be automated or if they’re one offs that benefit from human execution. Think blueprint vs. construction manual. What are your experiences with one or the other?

69

6 Comments

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

Is BDD just about tools & frameworks?   We dive into the true purpose & effectiveness of BDD with Jayapradeep Jiothis & Seema Prabhu!! #BDD #Testing #MastersofTheCraft #Podcast #Shorts

5

🎯 Why Wait for QA to Spot the Misalignments? I had an enlightening conversation with a Product Leader who praised his QA team for consistently identifying cases where the implemented product deviated from the requirements. But this is crazy: We shouldn't wait for QA to tell us we've implemented the wrong thing! For some products, QA is vital in uncovering edge cases and testing across various environments. Still, by the time a product reaches QA, the team should already be crystal clear on WHAT should be implemented. Unfortunately, that's often not the case. I firmly believe that engineers should be accountable for the quality of their implementation and ensure that what they build aligns with the product requirements. Yet, particularly in settings with offshore teams, I'm increasingly hearing that QA functions separately from engineering. This separation makes it even more crucial to define product requirements clearly and ensure everyone, including product, engineering, and QA, fully understands them. For smaller teams, this alignment might occur in person. However, as organizations grow and it becomes impractical for everyone to attend every meeting, the need for written documentation of detailed requirements becomes critical. 🌟 Alignment and a clear understanding of the WHY and WHAT we are building are crucial to success, and this alignment should happen before the implementation starts, not a second before the release. #ProductManagement #QualityAssurance #Engineering #Teamwork #Leadership

6

1 Comment

'No-code and low-code automation testing tools are transforming the landscape of software testing by making it more accessible and efficient. These tools enable faster test creation, easier maintenance, and broader participation in the testing process, ultimately leading to higher quality software'. If you have hands-on experience with any of these tools in your projects and would be happy to share your insights, please leave a comment or feel free to reach out to me directly. Your feedback will be invaluable for the analysis I’m conducting on this topic. I would love to hear from the QA experts out there about your thoughts and experiences with these tools. #NoCode #LowCode #AutomationTesting #SoftwareTesting #QA #TestAutomation #ContinuousTesting #SoftwareQuality #QualityAssurance #DevOps #CICD #TestingTools #TechCommunity #AutomationTools #SoftwareDevelopment #QualityEngineering

29

When I started testing, I was often asked to write a test plan for < a feature >. Or, sometimes, I’d be handed a 50 pager with the ask to “review the test plan”. These plans commonly detailed things like environment setup, OS, test steps, and other minutiae of how exactly the testing of < a feature > was to be executed. These days, I much prefer to write test strategies - instead of detailing every step, which inevitably leads to a lot of rework throughout the development process, we think strategically about how we can test certain aspects of our application, what kind of tests we’ll need and if those can be automated or if they’re one offs that benefit from human execution. Think blueprint vs. construction manual. What are your experiences with one or the other?

73

10 Comments

Please go through the blog for Microsoft Graph API and Playwright For Efficient Email Reading #QAAutomation Neova Solutions

2

Automating web components within a Shadow DOM is a common challenge for automation QAs. Playwright manages open Shadow DOM elements gracefully, and with some workarounds, it’s possible to interact with user-agent and closed components as well. In this blog, Arundev Nair discusses how the Testing Mavens team has addressed this challenge in our automation projects. We’d love to hear your feedback! Read the full article here: https://lnkd.in/gpz96F_2 #Automation #ShadowDOM #WebAutomation #TestingMavens #AutomationQA #Playwright #QACommunity #TestAutomation #TechBlog #AutomationTips #Seleniun #Testing

48

1 Comment

QA Automation Life: When your code runs perfectly… but only on your machine. 🤦‍♂️😂 There’s nothing like the feeling of tracking down that one bug that only appears at 3:00 a.m. or convincing a stubborn test script to behave. Automation isn’t just about writing tests — it’s about patience, problem-solving, and a lot of coffee. ☕️ To all my fellow QA automation warriors, what’s the funniest bug you’ve encountered? Share in the comments! #QALife #AutomationEngineer #TestingHumor #CodeBugs #TestAutomation

7

Testers need to be aware of the value they are providing - to the team, to the organisation, to the application or platform they are testing. It is too easy for companies and engineering departments to decide they are going to replace testers with AI or Automation. So, testers, don't just sit there waiting for requirements or acceptance criteria or detailed specs and expect everything to be handed to you. So you can copy paste those things into test cases and then mark pass or fail next each one. This approach is lower value work. More admin than testing. Get stuck in to whatever it is you are testing - learn the application, understand it, work out where there might be problems, go looking for them, discuss the application with engineers, with product managers, with customer services and onboarding, understand the users and their challenges, reproduce real customer issues, offer solutions and find a lot of bugs. Much higher value - and if this approach doesn't protect you from layoffs then at least you will have learnt a lot more. #QualityAssurance #ApplicationTesting #TesterValue

2

💡 Debunking Automation Testing Myths & Misconceptions 🛠️ Automation testing is an essential part of modern software development, but it's often misunderstood. This article clears up some of the most common myths and misconceptions surrounding automation testing and sheds light on the real story behind its benefits and limitations. If you're working in QA or test automation, this is a must-read to gain clarity on what automation can and can't do—and how to approach it strategically. Check out the full article here: https://lnkd.in/evFiSVkz #AutomationTesting #QA #SoftwareTesting #MythBusting #TestAutomation #QualityAssurance

1

Breaking News in Automation Testing! BrowserStack has teamed up with Selenium as their official development partner.🚀 What does this mean for the testing community? With BrowserStack's active role, this partnership is set to boost automation testing, helping Selenium improve client bindings, enhance documentation, build a more inclusive frameworks ecosystem, and support the community, To take advantage of this awesome team up, Secure your premium access to BrowserStack’s web automation platform and try out the latest Selenium features. Find out more here 👉https://shorturl.at/NnHyo #teatautomation #automationtesting #softwaretesting #testing #Selenium #BrowserStack #TestGuild

278

3 Comments

Interesting post by Gaurav Singh on balancing product and platform needs as a SDET. I've spoken to many Engineering leaders and I see 2 models: 1) SDETs embedded into Product teams and 2) Quality is folded into Platform as they focus on publishing common libs/tools. The actual writing and execution of tests are owned by the product developers. Both models can work but i'm seeing the trend towards approach (2). Curious to hear what has worked for others? #testingstrategies #QA #microservices #platformengineering

3

Now were taking real testing principals. These are fundementals worth learning until you can perform and teach them to others. If your hiring a Test Enginner or better yet, someone who coaches others in testing, look for these principals to be part of their conversation. Yes there are additional aspects to testing but these foundations will make a difference in the outcome of your work as a Test Engineer. Great job on sharing what really matters.

31

1 Comment

Why QAs are still underrated in Software Industry? 1) Missing the value of Quality "Quality is not an act, it is a habit.” — Aristotle Teams, companies picking up testing as a final checkpoint (mostly in startups) which drops the idea of testing. This perception undervalues the proactive role QA can play in identifying potential issues early, saving time and resources in the long run. 2) Creating a product which undermines End users This approach often leads to rushed testing phases, missed bugs, and ultimately, subpar products. Also can reduce usability of software. Due to such concerns the appeal of a product to users is reduced which ultimately leads to loss in business. 🌟 Misconceptions about QAs? 🌟 1) Development intellect & QA is Straightforward: This bias is probably created because of lacking coding skills by QAs. Although their are variety of designations now in the market like SDET, TAE, QE, etc. but these all convert actually into evaluating a product and making sure it meets the requirement. Hence gaining skills like programming, application architecture knowledge, domain knowledge, test automation are crucial to stay persistent in market. 2) Lack of education in QA: Organisations must invest in educating all team members about the importance and complexity of QA processes. Highlighting the skillset required for effective QA can elevate the role beyond the misconceptions. Quality is not just about finding bugs, it’s about preventing them and ensuring a seamless user experience 🌟 QAs being afraid of leading a successful team? 🌟 1) Recognition: is something which is needed by organisations and QAs should not be afraid of leading a team, if you have relevant skills as mentioned above then we can easily manage and create better products. These products would be better suited for end users usage! 2) Balanced Leadership: Having Dev & QA leads/managers/owners are becoming crucial as time proceeds with emergence of AI. Instead of focusing on repetitive tasks we need to take ownerships. This collaboration can bridge the gap between the two functions, fostering mutual respect and better outcomes Engg teams are core for a business growth, without its successful management Sales, Support, etc. cannot be standing anywhere. -x-x- To become a well rounded QA in 2024 & understanding coding, architecture, domains refer my Full Stack QA course here: https://lnkd.in/dWjpT3-3 Master Test Automation Frameworks and Design patterns: https://lnkd.in/gyFKz5yF #japneetsachdeva

65

2 Comments