Socium Recruitment’s Post

Full blog entry: https://lnkd.in/gCvb-dbY Team Names in Tech: Software engineers have a secret (sometimes not-so-secret) ego; as part of the human condition, they are typically skilled and take pride in their work, often eager to showcase their accomplishments, and sometimes reluctant to step forward individually. The modern workplace doesn't always embrace these aspects of the ego. Why not leverage this situation as a positive tool? Give your product groups Team Names and empower them to excel! It's not just about coding; it's about building a culture where innovation and team spirit thrive! For QA teams, incorporating team names into a Cypress automation project can be a valuable addition, fitting seamlessly with my open-source project that enhances the QA/Cypress experience. -> https://lnkd.in/gNFMeb88 #teambuilding #companyculture #techcommunity #innovation #employeeengagement #collaboration #leadership #creativityintech #workplacewellness

Hey👋 QA Engineer | SDET do you know that Playwright allows you to automate API tests ? Here are four key concepts that will help you develop your easy-to-maintain tests: 1️⃣ APIRequestContext: This class lets you execute HTTP requests, making it easier to interact with APIs. 2️⃣ AVJ (Another JSON Validator): This class simplifies the validation of JSON response schemas, ensuring that the data returned complies with the expected formats. 3️⃣ SOM (Service Object Model): A programming approach that helps you organise your code in a more structured and maintainable way. 4️⃣ Fixtures: These allow you to configure your test environment and avoid duplicating code. Thanks to fixtures, you no longer need to create a service instance for each use; they automatically manage the initialisation and reuse of the necessary service instances. Feel free to share any additional concepts or tips that can help as well ☀️ #Playwright #sdet #qaengineer

"I left this presentation with no better understanding of what an SDET is than what I came in with. There were some good recommendations of what NOT to do (ex: converting QA, using "failed" software devs), but I'm still not clear what an SDET is actually *doing* in their role." What an interesting comment after my presentation the other day. How would you have answered? https://lnkd.in/eTs8utSJ

Greetings, Software Development Engineers in Test (SDETs)! Buckle up for an epic adventure – your transformation into a legendary tester! This blog will be your trusty guide, leading you from manual testing proficiency to automation mastery across web, mobile, and API frontiers. #SoftwareTesting

🌟 Unlocking the Secrets of Silicon Valley's QA Success! 🌟 Ready to supercharge your QA team and boost your product's performance? Check out our latest blog post: "Silicon Valley Secrets: 3 Insider Tips for Building a Rockstar QA Team." Discover the keys to assembling a top-notch squad that'll elevate your software quality assurance game! 🚀 https://buff.ly/4azpLjk 🔍 #SoftwareQualityAssurance #QAteam #TestingTips #SiliconValleySecrets #TechExcellence 🛠️👩💻 Check

Ever wondered what it takes to become a top-notch Software Development Engineer in Test (SDET)? Let's delve into the insights of our seasoned SDET professionals as they share their perspectives on the must-have skills for success! From coding prowess to automation wizardry, their firsthand experiences will guide you on your journey to becoming an SDET pro. Stay tuned for a captivating exploration of the skills that can shape your future in the world of software testing!  #SDETProfessional #SkillsForSuccess #SoftwareTestingJourney #testautomation

🤩Diving deep into test automation and quality assurance has provided me with unique insights into the software development life cycle. As an SDET, I believe that robust testing isn’t just about finding bugs but ensuring a seamless user experience. Keen to connect with fellow SDETs and quality enthusiasts to share best practices, tools, and the future of testing automation. Let’s ensure the software of tomorrow is efficient, effective, and error-free. #QualityFirst #SDET #TestAutomation

Hot take: a truly professional SDET can be part of the Dev team, and meaningfully contribute, while still focusing on the testing aspect of work: ✅ Review prod code for quality ✅ Review unit tests for quality and gaps ✅ Be the advocate and driver of all things quality in the team ✅ But also change prod code, at least the simpler stuff I do recognize that organizational structure and silos may prevent you, an Individual Contributor, from doing the above things. And I don't expect anyone to reach such a level in the first 3 or even 5 years. But I do believe that's a reasonable end goal. This makes one think of what additional things one must learn. Because "ISTQB Foundation UI & API testing tool tweak Jenkins/TeamCity jobs" is FAR from everything. I'm also not saying that it must be the end goal of every tester. What do you think? #softwaretesting #testautomation #testing

Dev 2 QA? Embarking on the journey from software development to QA automation can be both a challenging and rewarding shift. How has your experience transitioning from development to QA automation shaped your understanding of the software development lifecycle, and what insights would you share with others considering a similar shift?