Dhawa Ngoche

Interviewing for your next role in software development doesn’t have to be stressful–not when we’ve got the inside scoop on what to expect and how to prepare.⚡ While having the technical skills is great, expressing how you’re a culture fit for the company is what can truly set you apart. Let’s break down the interview process. Step 1 💼 Initial screening Step 2 💼 Technical assessment Step 3 💼 Behavioural interview Step 4 💼 Additional interviews Curious to learn more? Check out our latest blog where we dig into the Top Interview Questions for Software Developers in 2024: https://lnkd.in/gNCPDHAZ

7

Code coverage doesn’t tell you as much as you think. Mutation testing sounds like a good verification measure. Has anyone used a mutuation testing framework for C/C++ or do you use Test Driven Development? Seems like TDD is the best approach.

5

There’s something for everyone in web development in here:

8

1 Comment

If you are deciding on PW vs CY for test runner, or thinking about transition, Take a look at: - https://lnkd.in/ehy5iCJk - and if you want to see Pw vs Cy on the same tasks: https://lnkd.in/eGhubPH3

10

It finally happened! 😱 Playwright beats Cypress in weekly downloads. In this video, we'll dive deep into the latest trend where Playwright has taken the lead over Cypress.io in the world of web automation testing. We'll discuss why Playwright is becoming the go-to tool for developers and testers alike and what this shift means for you and your automation projects. In my New Year’s trend report, I predicted that Playwright would become the number one browser automation testing tool this year, and that prediction seems to be coming true. But what does this mean for you? Now is the perfect time to enhance your web automation skills with the hottest testing tool on the market. 👇👇👇 https://lnkd.in/gK_Aeu-a #Playwright #PlaywrightvsCypress #testautomation #testautomationtool #automationtesting #automationtestingtool #softwaretesting #softwaretestingtool #automationtestingtrends #automationtestingtrends2024 #testguild

119

7 Comments

Unlock sharper insights and streamline workflows by unifying Marketing Mix Modeling and Incrementality Testing. Discover how this integrated approach can elevate your agency’s efficiency and effectiveness. #MarketingScience #AgencyEfficiency #DataDrivenInsights #MarketingAnalytics #StrategicGrowth #UnifiedApproach #CustomerSuccess LiftLab

1

When writing software, if you think writing tests are hard, detecting the root cause of the issue that arise after your code deployment is harder, and mitigating that issue without customer impact is the hardest. Be frugal, take the least expensive path and write your tests.

15

As a C# developer I found this informative; it’s about an alternative way to structure unit tests. I would certainly try this. Here’s a blog by my colleague.

2

What are some of the biggest myths about quality assurance? Want to know how to streamline GraphQL service testing? Can you use a no-code approach to help with performance testing Find out in this episode of the Test Guild New Shows for the week of July 14. So, grab your favorite cup of coffee or tea, and let's do this.   Featuring automation awesomeness contributions from: Vitaly Sharovatov Qase Jason Arbon trivago Armin Aminian Giuseppe Donati Karate Labs Chris Rolls Stephane Landelle Shaun B. Gatling Venue.sh Tracebit and more!    ** ALL LINKS W/TIMESTAMPS IN THE FIRST COMMENT BELOW ** #devsecops #automationtesting #softwaretesting #performancetesting

54

14 Comments

There are two types of mid-level software developers out there: First: Those teaching and sharing how to handle thousands or millions of transactions per second (100K tps). Second: Those avidly watching and reading about how to handle thousands or millions of transactions per second. Meanwhile, both are working on systems that barely handle 10 transactions per second on a good day. #ScalableSystem

13

1 Comment

⏲️🚩🥊 Why do engineering teams tend to fight to keep feature flags temporary? Three things that suck about permanent flags: 🤯🧪 It is challenging to test different variants in your code — every permanent flag adds a power of two to the possible combinations 🤔🤷 We don’t capture intent — should this flag cleaned up or meant to be left more permanent? 🎛️🚧 Improper safety controls to mitigate risk — if logic is permanently dynamic, will that cause issues when changed?

7

I learned something new yesterday about "printf" and format specifiers. While it might be familiar to most Java developers, it's new to me as I'm still learning. Here are some commonly used format specifiers: %d: Integer %f: Floating-point number %s: String %c: Character %b: Boolean Coding is a journey, and each day brings new insights! 💻💡 #softwaredevelopment #java #algorithms #dsa #programming #softwareengineering #qaengineer #qaautomation #womenengineers #womenintech #linkedintopvoice #tech #swe #devlife #coding

57

8 Comments

#playwright 1.45: Mastering Time and Flaky Tests! Exciting news, Playwright developers! Version 1.45 is here, bringing powerful new features to enhance your testing experience. Time Travel for Tests with the Clock API ️ Say goodbye to unreliable time-based tests! The new Clock API lets you control time within tests, simulating various scenarios like: Testing with predefined times: Set a specific time for your test to run in a controlled environment. Consistent time and timers: Ensure timers and other time-dependent elements behave as expected. Monitoring inactivity: Test how your app handles periods of user inactivity. Manually ticking through time: Simulate time progression within the test for granular control. Example: JavaScript // Set time to Feb 2nd, 2024, 8 AM await page.clock.install({ time: new Date('2024-02-02T08:00:00') }); await page.goto('http://localhost:3333'); // Simulate user closing/opening laptop at 10 AM, then pause time. await page.clock.pauseAt(new Date('2024-02-02T10:00:00')); await expect(page.getByTestId('current-time')).toHaveText('2/2/2024, 10:00:00 AM'); // Simulate another period of inactivity, then assert updated time. await page.clock.fastForward('30:00'); await expect(page.getByTestId('current-time')).toHaveText('2/2/2024, 10:30:00 AM'); Use code with caution. content_copy Taming Flaky Tests with New Options --fail-on-flaky-tests: This new CLI flag sets the exit code to 1 when any flaky tests occur, ensuring test runs fail without successful retries. PLAYWRIGHT_FORCE_TTY: Control the behavior of built-in reporters in CI environments. Set to 0 to disable ANSI control sequences, or specify a terminal width for proper formatting. Additional Enhancements ✨ Respect Git Ignore: New options allow excluding files matching .gitignore patterns when searching for tests. Timeout for Custom Matchers: Custom expect matchers now have a timeout property to control timeout behavior. Directory Uploads: Upload entire directories for webkitdirectory elements using locator.setInputFiles. Control or Meta Modifier: Use ControlOrMeta for keyboard shortcuts that map to Control on Windows/Linux and Meta on macOS. Enhanced API Request Control: New options for apiRequest.newContext and apiRequestContext.dispose provide more granular control over authorization and context disposal. Websocket Connection Control: Specify a custom host address when launching a WebKit server with browserType.launchServer. Ubuntu 24.04 Support: Playwright now supports Chromium, Firefox, and WebKit on Ubuntu 24.04. Important Note: This is the last Playwright release with WebKit updates for macOS 12 Monterey. Please upgrade your macOS to continue using the latest WebKit. For detailed information, check out the Playwright documentation! Sanjay Kumar Mukesh Otwani Rahul Shetty Naveen Khunteta Artem Bondar Artem Golubev Symon Storozhenko Tarek Roshdy Michal Drajna https://lnkd.in/gZPb23Hi

5

Don't overlook the 'annoying tasks' that an engineering team becomes accustomed to over time, instead, build a culture where they are solved. “Great DevEx shortens the distance between intention and reality” https://lnkd.in/eZYr9Zbe Don't patch over problems, kill them. In terms of multiplying team velocity, reducing speed bumps caused by bad tooling and process is extremely high impact. As a manager, some problem areas to keep an eye on: * Developers finding it 'hard' to push/pull from any repos needed by the team * Difficulty updating and/or sharing secrets/keys between team members securely * Wasted time going 'back and forth' on merge requests for issues that can be solved by automation (linting, formatting, etc) * Cultural norm of 'ask person X' how to perform a specific task vs. playbooks/documentation - siloing / locked knowledge Any other high impact ones I'm missing?

3

1 Comment

Work today can leave software developers feeling unconnected, lonely, maybe disassociated. The focus on teams and groups doesn't always lead to connection. Leaving some behind or working alone anyway. We need pair programming more than ever (or at least some version of a diadic working relationship). To find out why, start at 23:28 of "A company is not a family with Airbnb CEO Brian Chesky". They shone some light on the psychological benefits of working in pairs. (then, start from zero because the rest is great too!) https://lnkd.in/g58QN9mf You can't force a bond. However, it might be useful to pair up with differently skilled so there's a balance and a mutual benefit. The mentor-mentee pair can work too but I suspect it depends on being in a sweet spot in terms of power distance; even then it might not be as strong. Various combos of diads and sometimes triads make the world go around and make our days that much better!

8

1 Comment

🚀 Master System Design Interviews with the D.E.S.I.G.N. Method! 🔍 Struggling with system design interviews? Learn a structured approach to tackle them with confidence. 🌟 Invented D.E.S.I.G.N. Framework: This post introduces the innovative D.E.S.I.G.N. Method to help you excel in system design interviews. 📋 D.E.S.I.G.N. Method: 1️⃣ Define and Clarify: Capture requirements and ask clarifying questions. 2️⃣ Establish Architecture: Develop a high-level design and visualize components. 3️⃣ Specify Components: Dive into details like user authentication and data structures. 4️⃣ Identify and Mitigate: Plan for edge cases and potential failures. 5️⃣ Gauge and Optimize: Identify bottlenecks and optimize performance. 6️⃣ Nurture Scalability: Plan for future growth and scalability. 🛠️ Real-World Example: See how this method works for designing a scalable e-commerce platform. 👩‍💼 Interviewer and Interviewee Dialogue: Understand how to apply the method in a real interview setting. 🔗 Read the full post to master your next system design interview! 👍 If you found this helpful, follow, clap, and share it with others! https://lnkd.in/gm5QdYTE #SystemDesign #InterviewPrep #EngineeringManagement #TechInterviews #CareerTips #SoftwareEngineering #TechIndustry #ECommerceDesign #DESIGNFramework HackerNoon Saurabh Shrivastava Neelanjali Srivastav Dhiraj Thakur

8

The difference between tests absolutely is vibes. Especially when it comes to things that aren't traditionally "software", like infrastructure. The entire difference between unit, integration, and end to end becomes mostly meaningless By the way: test your infrastructure. It's hard and it sucks, but it's also super important. That said, unit tests for infrastructure are basically end to end tests for anything else. It's fine, lean into it and don't worry too hard about semantics. (but it does mean test driven development probably isn't happening the traditional way. Waiting 20 minutes to launch a fleet of infrastructure in the cloud is absolutely a unit test but it's not a thing you're gonna do hundreds of times a day and expect to get work done, much less in a "run the tests on save" style of work)

25

With testing, it's not possible to prove that a system has no bugs. That would take infinite tests, and honestly who has the time? But it only takes one test to *refute* that the system has no bugs. Provided our expectation about what the system's supposed to do in that scenario is *refutable*.

27

18 Comments