search
HomeWeb Front-endJS TutorialOn to effective frontend testing
On to effective frontend testingSep 14, 2024 am 06:18 AM

On to effective frontend testing

Have been interviewing for quite a while. What stood out to be in this painful process was that the interview is doomed if the question of testing was raised at all. This is because my experiences have been primarily in frontend development and the two companies I have stayed in were very poor in frontend testing.

--- Skip if you want to go straight to the discussion ---

My lack was, in some sense, a byproduct of industry culture. Frontend testing has always been a thing, but back a decade ago company structure has been separating testing concerns from development process. So we had a dedicated QA team who would write E2E/automated tests for us developers. So testing was not even in the job description. Also the unfortunate truth of small startup is delivery is always above everything else, so since testing hinders productivity, we developers didn't test. We didn't even have any testing librarie (Jasmine/Mocha/PhantomJS...) installed in the repo.

I got my second job in a much bigger company (consumer platform team had like 150 developers?). However, there was no testing too essentially speaking. Each team (teams divided by feature like checkout, loyalty, registration...) again had dedicated QA member(s) who would write those E2E test. Once that culture set in and QA was cut from the budget, no one was picking them up because there was no one to learn it from. I tried to pick up some E2E testing for our team, but the code left behind wasn't even functional and full of obvious bugs (lots of WTFs). Combined with tight deadlines AGAIN, testing fell behind. The only time people talked about testing was for utility functions and custom react hooks.

--- discussion starts ---

Being plagued by the no-testing culture, I have to at least come up with something that I can say during interviews about testing abstractly. I'll skip over the usual bullshits of not testing styles or implementation what not.

Feel free to add to the discussion. This affects at least 300 of my past coworkers!

1.) test global states:
In my experiences one of the most gnarly feature is "if this happens, we'll do this for you automatically" type of behavior. For example, one app I had was a graph visualization dashboard that was heavily configurable. One configuration change can cause other configurations to change as well, depending on the data returned and what not. Some configuration side effects are not straight forward. So you'll want to test automatic configuration changes and whether the state is persisted/unchanged/consistent across the board. So if you have testing around this type of behavior, aligned with PM, managers, design, and QA team is immensely vaulable.

2.) don't spend much time testing the integrity of UI input:
I see quite a few tutorials talking about testing inputs, like when I type "taylor swift" into the search bar and press enter, then our search function will get taylor swift as input.

This is straight up unhelpful. If your data binding is broken it'll either be very obvious that you should have caught it yourself while development or it's not automatically testable because something was hindering the functionality, like an invisible div above search bar so users can't type in search.

if you are being paid by lines of code though, go ahead :)

3.) test inputs as side effect of inputs though is desirable:
contrary to number 2, you'll want to test functional calls that are completely side effects to user interaction. For example, when user clicks on a button, a request should be called to register this user action for data analysis. This type of side effect that are completely separate from the core functionality, should be automatically tested so that we won't be caught off guard by some unintentional changes. Non-core side effect can be essential to other teams, I was on one of such other teams :D

So how do you architect these testing requirements?
let's break down the frontend architecture: MVC (you can say you are MVVM or what not, it doesn't really matter).

V - view (html/jsx): This is great for E2E/headerless browser testing and is an industry standard.

C - controller (business logic): spend some time making sure the functions are correct. For example, if you have/abstract to pure functions, does the expected input-output process still in tact? Somewhat industry standard, but people don't usually bother making stateful functions into pure functions and test.

M - model (api calls/states): this is what I want to focus on the most. your (non-rendering) states should be global and singleton per concept. Not new idea, since Redux is basically it. However it doesn't have to be Flux for our testing purposes. You can have jotai atoms but you can code a wrapper so that you can expose your centralized setter functions for testing.

the similar thing should be done on your api calls/third party libraries. It should be global and singleton so that you can confidently tests "when I do this, is a core/noncore api call made in the application". This is done routinely in, my limited experience, backend applications. It should be done in frontend applications too.

How does this sound? I am sure someone already does this already, what's your experience? what can be improved? I'd love to hear from folks where frontend testing just go beyond E2E/headless browser and braindead simple unit testing.

The above is the detailed content of On to effective frontend testing. For more information, please follow other related articles on the PHP Chinese website!

Statement
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn
Replace String Characters in JavaScriptReplace String Characters in JavaScriptMar 11, 2025 am 12:07 AM

Detailed explanation of JavaScript string replacement method and FAQ This article will explore two ways to replace string characters in JavaScript: internal JavaScript code and internal HTML for web pages. Replace string inside JavaScript code The most direct way is to use the replace() method: str = str.replace("find","replace"); This method replaces only the first match. To replace all matches, use a regular expression and add the global flag g: str = str.replace(/fi

8 Stunning jQuery Page Layout Plugins8 Stunning jQuery Page Layout PluginsMar 06, 2025 am 12:48 AM

Leverage jQuery for Effortless Web Page Layouts: 8 Essential Plugins jQuery simplifies web page layout significantly. This article highlights eight powerful jQuery plugins that streamline the process, particularly useful for manual website creation

Build Your Own AJAX Web ApplicationsBuild Your Own AJAX Web ApplicationsMar 09, 2025 am 12:11 AM

So here you are, ready to learn all about this thing called AJAX. But, what exactly is it? The term AJAX refers to a loose grouping of technologies that are used to create dynamic, interactive web content. The term AJAX, originally coined by Jesse J

10 Mobile Cheat Sheets for Mobile Development10 Mobile Cheat Sheets for Mobile DevelopmentMar 05, 2025 am 12:43 AM

This post compiles helpful cheat sheets, reference guides, quick recipes, and code snippets for Android, Blackberry, and iPhone app development. No developer should be without them! Touch Gesture Reference Guide (PDF) A valuable resource for desig

Improve Your jQuery Knowledge with the Source ViewerImprove Your jQuery Knowledge with the Source ViewerMar 05, 2025 am 12:54 AM

jQuery is a great JavaScript framework. However, as with any library, sometimes it’s necessary to get under the hood to discover what’s going on. Perhaps it’s because you’re tracing a bug or are just curious about how jQuery achieves a particular UI

10 jQuery Fun and Games Plugins10 jQuery Fun and Games PluginsMar 08, 2025 am 12:42 AM

10 fun jQuery game plugins to make your website more attractive and enhance user stickiness! While Flash is still the best software for developing casual web games, jQuery can also create surprising effects, and while not comparable to pure action Flash games, in some cases you can also have unexpected fun in your browser. jQuery tic toe game The "Hello world" of game programming now has a jQuery version. Source code jQuery Crazy Word Composition Game This is a fill-in-the-blank game, and it can produce some weird results due to not knowing the context of the word. Source code jQuery mine sweeping game

How do I create and publish my own JavaScript libraries?How do I create and publish my own JavaScript libraries?Mar 18, 2025 pm 03:12 PM

Article discusses creating, publishing, and maintaining JavaScript libraries, focusing on planning, development, testing, documentation, and promotion strategies.

jQuery Parallax Tutorial - Animated Header BackgroundjQuery Parallax Tutorial - Animated Header BackgroundMar 08, 2025 am 12:39 AM

This tutorial demonstrates how to create a captivating parallax background effect using jQuery. We'll build a header banner with layered images that create a stunning visual depth. The updated plugin works with jQuery 1.6.4 and later. Download the

See all articles

Hot AI Tools

Undresser.AI Undress

Undresser.AI Undress

AI-powered app for creating realistic nude photos

AI Clothes Remover

AI Clothes Remover

Online AI tool for removing clothes from photos.

Undress AI Tool

Undress AI Tool

Undress images for free

Clothoff.io

Clothoff.io

AI clothes remover

AI Hentai Generator

AI Hentai Generator

Generate AI Hentai for free.

Hot Article

Hot Tools

PhpStorm Mac version

PhpStorm Mac version

The latest (2018.2.1) professional PHP integrated development tool

MantisBT

MantisBT

Mantis is an easy-to-deploy web-based defect tracking tool designed to aid in product defect tracking. It requires PHP, MySQL and a web server. Check out our demo and hosting services.

SublimeText3 Linux new version

SublimeText3 Linux new version

SublimeText3 Linux latest version

SecLists

SecLists

SecLists is the ultimate security tester's companion. It is a collection of various types of lists that are frequently used during security assessments, all in one place. SecLists helps make security testing more efficient and productive by conveniently providing all the lists a security tester might need. List types include usernames, passwords, URLs, fuzzing payloads, sensitive data patterns, web shells, and more. The tester can simply pull this repository onto a new test machine and he will have access to every type of list he needs.

EditPlus Chinese cracked version

EditPlus Chinese cracked version

Small size, syntax highlighting, does not support code prompt function