Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhat is the best alternative to Browsersync?
Top Pro
Top Pro
Top Pro
Top Pro
Top Con
Top Con
Top Con
Top Con
Top Pro
Top Pro
Everything you need to get a project started is included with CodeKit. Thanks to the professional support, different components of the workflow pipeline are guaranteed to play nicely with each other without you needing to do the research on how to configure them. More advanced features that may require extra configuration to set up with other workflow wrappers are set up out of the box in CodeKit, like automatic browser updating, linting, and source maps. See More
CodeKit has a clean and intuitive graphical user interface out of the box. Most other tools in this category run as command line utilities or require unsupported third-party plugins to run with a GUI. The CodeKit GUI makes it easier to navigate and manage the various components of your project with helpful UIs like dropdowns, and views that provide extra details without having to run a separate command. See More
CodeKit has live updating built in and will update monitored files across multiple browsers and devices, and refresh CSS without a new page load. Other workflow wrappers have live updating, but they require extra configuration. With CodeKit, everything is set up for you so you can get it up and running in no time at all. See More
Ghostlab utilizes weinre, an open-source remote debugger to remotely inspect the code on different devices. By double clicking the device name that needs to be inspected, and clicking the 'Debug' button, Ghostlab opens a Chrome inspector which can inspect any item in the page of the device and manipulate the CSS and HTML. See More
You'll often end up having PhantomJS binaries connected via WebDriver to your testing framework, possibly using client/server especially if you want your test running with something else than Java. This means an overhead in terms of maintenance and performance, but still usually lighter than running a full browser (like Chrome, Firefox, IE). See More
It often happens when running on more then 5 (my measurement) JVM instances that the browser gets stuck and quits unexpectedly. This can be partially solved by running the instances one by one instead of parallel (this is a problem when testing Jenkins and Bamboo agents) but I don't believe this qualifies as a solution. The error is called UnreachableBrowserException. See More
This is an error which occurs with almost no reason, PhantomJS sometimes decides that it cannot click the element even though the element is intractable or enabled. This happens if you have to scroll to see the element (and these are not pages that load elements with JavaScript) which is strange because PhantomJS should catch the whole page if it is not loaded explicitly with JavaScript. This problem partially goes away with re-sizing the browser, but that does not really qualify as a solution. The error it raises is: ElementNotVisibleException. See More
If you are using the free plan, keep in mind that the test suites created there are scheduled to be deleted after around 2 weeks. Endtest will send you a notification email the day before mentioning "Test suites from users who are not on the PRO Plan get automatically deleted after some time," and offering for you to upgrade to PRO. See More
The free plan covers a lot, you can have up to 3 test suites, and you can run your automated tests as many times as you want. The pro plan includes some very advanced options that you might need only if you're working with a team (for example, the collaboration feature, schedule test run, API for Jenkins, etc.). See More
Setting up Adobe Edge Inspect is rather easy. The Edge Inspect application itself is needed for desktop and a chrome plugin. For mobile devices, there is the Adobe Edge Inspect mobile app which needs to be installed. Once the Inspect program is "switched on", it will start watching all devices that have Edge Inspect enabled. For mobile devices, the Inspect app will generate an authentication code which needs to be inserted into the Chrome plugin. Once that's done, the devices are synchronized. See More