1 / 1

Takefumi Yoshii: Introduction to Testing for Frontend Development

$46.00USD
1
Free Priority FedEx · on orders over $300
Shipping available to United States
Estimated arrivalNov 11 – Nov 14
Exact shipping options and rates are shown at checkout.
From South Korea
In stock
From United States
Unavailable
Description

Test automation is important for the quality and maintainability of modern web applications, but many developers find writing tests difficult because they have never done it before. This book is for front-end developers writing test code for the first time. It explains basic testing techniques, how to write tests for different situations, and how to use a variety of tools, with plenty of examples. In particular, its examples built with TypeScript and Next.js teach current practical knowledge and techniques. The Korean edition adds appendices on running UI component tests and E2E tests in GitHub Actions, making the book even more complete.

Korean title: 프런트엔드 개발을 위한 테스트 입문

Korean author: 요시이 다케후미

Korean publisher: 제이펍

ISBN-13: 9791193926260

Reviews

5.0
Based on 10 reviews
Showing 8 of 10 reviews
TO******
July 21, 2024

A book that helps you become a testing expert. A book that teaches testing techniques you did not know. It helps you talk about testing with confidence. It seems like mastering this one book could be enough to get you a job.

SA******
July 16, 2024

Front-end tests are needed to check that the user interface works correctly, prevent bugs in advance, and minimize the effect of code changes on existing features. To test, you first need to learn basic concepts and terminology, along with the relevant technologies and tools. Once you choose an appropriate test framework and tools—such as Jest, Mocha, or Cypress—you can set up an environment for running tests. It is common to start small with simple unit tests and gradually expand to more

CJ*****
July 13, 2024

According to translator Bae Eon-su's preface, not many teams wrote tests in their day-to-day work while the translator was working in Japan. Many developers give up on testing UI development because of a vague assumption that writing tests is difficult. But there is a big difference between deciding something is unnecessary based on sufficient knowledge and reaching that conclusion based on a vague impression. To save costs, tests can be used to exempt frequently unchanged areas from regression

DA****
July 11, 2024

During a recent job interview, I was asked, “Have you ever written test code while developing?” I answered that I had never applied it to a project in earnest. Afterward, I resolved to learn how to write tests properly. While looking for paid courses and YouTube videos about testing, I had the good fortune to come across this book. 🌱 Contents: CHAPTER 1 Testing Goals and Obstacles; CHAPTER 2 Testing Methods and Strategies; CHAPTER 3 Getting Started with Unit Testing; CHAPTER 4 Mock Objects;

CP*****
July 8, 2024

Book reviews sponsored by publishers (Language: Korean). I was selected for JPub Publishing's third IT Professional Book Reviewer cohort and received a copy of the book. Although its official difficulty rating is said to be the lowest, you should absolutely not choose this book when you are first learning to code. Its beginner-level rating is for people who already work as front-end developers. If you have at least built a decent website on your own using HTML, CSS, and JavaScript, you may be

KI*******
July 5, 2024

I had often heard terms such as TDD, white box, and black box mentioned only superficially as keywords, but I often found it daunting to go from seeing examples to applying them directly to a project. This book includes: new example code written last year, based on Jest, a testing library for the modern front end (Next.js). Since online searches for testing code mostly turn up outdated Java-based material focused on back-end code, I think this is a major advantage; coverage from terminology

OO*****
July 3, 2024

On code reliability, one way to distinguish SI companies from service companies is whether they write tests, though that is not true of every company. For an SI project, something is not a problem if it is not specified in the contract. The client's requested features just need to work, and the service needs to earn more than it cost to develop. If the client decides the profit is too low, you might get hit with a lawsuit—that can be a scheme to cut the final payment. By contrast, service

HO******
July 1, 2024

As I began writing tests for individual pages at work, I realized I needed to learn more. I watched online courses and read various articles, but the information was fragmented and frustrating. This book clearly explains the points I found confusing and shows, with a range of code examples, how to apply them using Jest and Playwright. It balances easy-to-understand explanations of the concepts with varied code examples. The material, from unit tests through E2E tests, is substantial and has

요시이 다케후미: 프런트엔드 개발을 위한 테스트 입문
12 items