this post was submitted on 12 Sep 2023
15 points (94.1% liked)

Web Development

3440 readers
14 users here now

Welcome to the web development community! This is a place to post, discuss, get help about, etc. anything related to web development

What is web development?

Web development is the process of creating websites or web applications

Rules/Guidelines

Related Communities

Wormhole

Some webdev blogsNot sure what to post in here? Want some web development related things to read?

Heres a couple blogs that have web development related content

CreditsIcon base by Delapouite under CC BY 3.0 with modifications to add a gradient

founded 1 year ago
MODERATORS
snowe
erlingur
Ategon
15
Avoiding tunnel vision when debugging (feddit.uk)
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/webdev
8 comments fedilink hide all child comments
 

Hey guys! Sorry if this isn't the best place for this but I couldn't really find anywhere else.

I've been working for 6/7 years as a web developer full-time now, and I'm still plagued by one mega frustrating habit. When I'm working on something complex on one page, and it gets completed, I'll fairly often get notified either by the client or my boss a day or two later while they're testing the whole site that there's something broken on another page.

Almost always, it'll be down to the fix I've recently made.

Is there a way to avoid this kind of tunnel vision? I try to keep my code localised as much as possible, avoiding interacting with global scope and, if it's really for one specific thing, tying it down to that page in particular, but short of testing the entire site every time I make any change... is there anything else I can do?

Thanks!

you are viewing a single comment's thread
view the rest of the comments
[–] alr 4 points 1 year ago

Check what your testing organization is using first. We're using Selenium at work, except for one small team that used Cypress because they couldn't be bothered to find out what the test of us were using, so now that team is faced with either maintaining their own version of the CI pipeline and their own tooling (and not having anyone to ask for advice) or rewriting all of their tests. Not an enjoyable choice to have to make.