Aussie living in the San Francisco Bay Area.
Coding since 1998.
.NET Foundation member. C# fan
https://d.sb/
Mastodon: @[email protected]

  • 0 Posts
  • 158 Comments
Joined 1 year ago
cake
Cake day: June 14th, 2023

help-circle




  • I moved from Windows 10 to Fedora/Debian recently. Dual-booting them until I figure out which one I want to use. I’ve used Debian on servers for 20+ years, but Fedora seems like a great distro too. I switched to Fedora at work too, and I’m enjoying it. At work, I can choose between a MacBook with MacOS, or a Lenovo ThinkStation or X1 Carbon / P1 with Windows or Fedora.

    The only Windows-specific app I really cared about was Visual Studio, but Jetbrains Rider is looking like a good replacement. I don’t really do any PC gaming any more.




  • We know that in every single example so far that Monopoly and Competition inversely correlate by definitions

    A direct (not inverse) correlation between them happens all the time in tech. Smaller companies get sick of the market leader or monopoly for some reason, produce a better product, and people switch over.

    For example, Internet Explorer had a web browser monopoly. Around 98% of web users used it. It lost that monopoly not because it was shut down, but because other, better browsers were released and people organically switched over. Increasing the competition reduced its monopoly.

    The same could be said about Teamspeak users moving to Discord. Teamspeak had a monopoly on real-time gamer chat, but people moved to Discord because it was better.








  • dan@upvote.autoProgrammer Humor@lemmy.mlOverflow
    link
    fedilink
    arrow-up
    5
    arrow-down
    1
    ·
    edit-2
    21 days ago

    In E2E tests you should ideally be finding elements using labels or ARIA roles. The point of an E2E test is to use the app in the same way a user would, and users don’t look for elements by class name or ID, and definitely not by data-testid.

    The more your test deviates from how real users use the system, the more likely it is that the test will break even though the actual user experience is fine, or vice versa.

    This is encouraged by Testing Library and related libraries like React Testing Library. Those are for unit and integration tests though, not E2E tests. I’m not as familiar with the popular E2E testing frameworks these days (we use an internally developed one at work).