JAVASCRIPT APPLICATION Frontend Backend Handling UI functionality: web, apps, desktop Handling business logic, data store connection A B We will focus on the Frontend for this session.
WHY DO WE NEED? Bugs are bad, and who gets blamed? The developer. You know humans are bad at complex, repetitive tasks. Computers are very, very good at complex, repetitive tasks. A professional ships working code. Code that works. Code that is well tested.
Focused on input & output. Not interested about the things happening inside. Involve testing of the internal structure, code, design & implementation. METHODOLOGIES BLACKBOX WHITEBOX
Very fast feedback Can not reproduce functional bugs faced by users STATIC TEST: PRO & CONS We can mark it as mandatory Very beneficial in the development phase
Fast feedback Need an extra effort to write UT UNIT TEST: PRO & CONS Verify the correctness of the function Can not represent the bug when the unit integrated Can not represent real user interaction
Verify most of user interactions Slower feedback than UT More effort than UT INTEGRATION TEST: PRO & CONS Can not represent device variant Can not replicate using the real data
END-TO-END TEST A robot that behaves like a user to click around the app and verify that it functions correctly. Tools: ● Cypress ● Nightwatch ● TestCafe
CREDITS: This presentation template was created by Slidesgo, including icons by Flaticon, and infographics & images by Freepik and illustrations by Stories. THANK YOU Please keep this slide for attribution.