I also would like to know if you support ReactJS applications.
Hello! I would also like to know if there are any improvements in relation to this discussion. I will have to test a new product and its build is based on components created from React. i donāt have access to the product yet, but i can point out to the developers to add attributes like [name=]
Hi there,
Thank you very much for your topic. Please note that it may take a little while before a member of our community or from Katalon team responds to you.
Thanks!
I believe that there is no change with this respect in the newer versions of Katalon.
In the E2E testing perspective, a react app is just an HTML+CSSļ¼JS opened in a browser window. You can work on it using Selenium WebDriver. See this post for evidence. However, I personally have a doubt if Selenium WebDriver (and its derivertives including Katalon Studio) is an appropriate tool to test the modern JavaScript-based apps. These apps are completely event-driven by JavaScript. On the other hand, the WebDriver API was originally designed with a combination of dum web browsers and functionally-heavy server side app that responds HTML + CSS and a bit of toy JavaScript, which was pupular in approximately 20 years ago. The WebDriver API can not cope with the modern JavaScript apps with promise, await. If I write a Test Case in Katalon Studio for a React app, I have to insert a lot of waitFor* keywords to trace the events by monitoring the changes observed in the DOM. This is difficult like an interpreter job of 2 different human languages. I wouldnāt say itās impossible, but could be hard. I would rather write detail tests for React app in JavaScript natively using Jest while calling my functions in JavaScript directly. A book on React.js advized me so. This makes sense to me.
Perhaps, I would mix Selenium WebDirver-based tests and Jest-based tests to cover the full aspects of UI testing of a web site which is internally built upon React.js. The WebDriver is suitable to verify the outer aspects of a web site, The JavaScript-native test is suitable to look at the internal of react app. I would employ both approaches. One tool does not cover all.
Have a look at my recent post:
1 Like