Swap out test data with Datasets!

Happy Valentines, everyone!

This is our first release note of the new year, and we’re happy to announce the release of Datasets for UI-licious Studio!

Datasets lets you configure different sets of test data to run a test with.

It’s useful when you want to:

  • Setup tests for different environments e.g. staging, production
  • Test the same user journey but for different roles
  • Store sensitive test data like passwords that cannot be written in plain text in the test scripts, and also mask them in test reports.

(Note: Datasets is only available on the professional edition of UI-licious Studio. …

IE11 support, highlights for interaction commands, user agents configuration, full page screenshots, and more!

Run Tests on IE11

If you don’t need to support IE11, good for you!

But if you are stuck with having to develop for IE11, there’s finally good news!

After two years of building UI-licious, we now support testing on IE11. 🎉 This is available to Pro Plus users.

I don’t blame the browsers for not getting test automation right using the WebDriver protocol standards, because the specs aren’t exactly the clearest, and THEY KEEP CHANGING, BLOODY HELL.

We’re super happy that we‘ve finally gotten here. One of the core philosophies that Eugene and I decided when we first started building UI-licious was that…

You can now run tests on Safari, and from specific regions — California, Frankfurt, Singapore, Japan, Taiwan. Prettier reports on the Editor with more information. And setup Slack / webhook notifications for scheduled jobs.

🌟 What’s new

Time to tame the Safari. Photo by Ron Dauphin on Unsplash

Run tests on Safari

You can run tests on Safari. This is currently under Beta, as we are still working on improving the performance of Safari tests. You can select Safari from the Editor now. [Pro users only]

Test your app in specific regions

Microsoft Edge, cookies and cake. Yum.

We’re working to support more browsers as soon as possible. And now, you can run your tests on Microsoft Edge. We’re also refining the test scripting library to test more scenarios and have added commands for you to set and test cookies.

🌟 New stuff

  • You can run your tests on Microsoft Edge (only for Pro accounts) —Microsoft Edge deserves a kudos for behaving like a good browser *cough* unlike Safari *cough*
  • You can set and assert cookies.
  • You can use SAMPLE.id to generate random base58 strings to use as sample data.

💪 Enhancements

  • Improve performance of retrieving live reports
  • Updates to I.fill: Target elements by XPATH, aria-label, and current value
  • Updates to I.click: Target elements by aria-label, and the current value and placeholder for visible input fields
  • Updates to I.see: Target elements by the current value and placeholder for visible input fields
  • Added I.type command as…

🚀 Version 1.5.0 Released

It’s finally here!

We heard you, and we’ve been working hard to build what you want. Here’s what you have been waiting for: Test Scheduling!

🌟 New stuff

Schedule a test

You can create a job to schedule tests to run any day any time. When something catches 🔥, we’ll send you an alert.

Go to your project space, you’ll see a new tab: Monitoring. Here, you can see your list of scheduled jobs and schedule new ones.

Schedule a test to run

Tests can be scheduled to run for multiple browsers at a time. And you can set the email address to send alerts to when there’s a 🐛.


1.4.0. Test configurations, more shortcuts.

We’ve released a new version of the UI-licious Studio and Test Engine, to make automating web application test simpler and more robust.

We’ve added new commands and configurations to give you more control over your tests, and made performance optimisations to the Studio.

Note that there is minor breaking change with tab switching. Sorry about that! But, the good news is that the fix is pretty simple.

💔 Breaking Changes

  • When I.click opens a page in a new tab, the browser will be automatically switched to it. If you are using I.switchTab to switch tabs after I.click, you can remove I.switchTab, or (not…

We have some exciting news! We have expanded our conquest of testing everything on the web to Web Components! Polymer is now a supported framework!

What’s new:

  • Support testing for Web Components. Yes, we promise to test every element and shadow on the web.
  • Added I.grabText command to read text from an element on the webpage to use as input for later test commands:
// Imagine you just finished ordering a pizzaI.see("Thank you for ordering UI-licious pizza. Your order number is");var orderId = I.grabText("#orderId"); // read the text from the #orderId element on the webpageI.goTo('/orders'); // go to your…

The women at Google I/O 2017. Credits: Women Techmakers

This year, we’ve hit a milestone in having 25% women attendees and speakers. For the first time at a tech event, I spoke to more women than men because I’m not nearly one in a handful.

Throughout the event, I’ve meet several wonderful women from diverse cultural background, at different stages of their study/career, deeply passionate about their work, proudly contributing to different areas in tech — beyond the stereotypical design or project management roles. Here are some of them:

Juana: Front-end engineer at a startup

Wendy: Andriod developer who made an app to help people discover public art in…

It’s has been a busy time for us for the past two months since EF’s Demo Day, but we are still hard at work pushing new features and polishing our system!

We’ve released a new version!

To make testing easier, we’ve added new commands, shortcuts, and improved the interface of the editor. You may have already noticed some of these changes which have been quietly released over the past month.

What’s changed in version 1.2.0?

  • 💬 Added chat box so that you can talk to our technical team!
  • Added shorter commands to save keystrokes:
  • I.fill — Shortcut for I.fillField
  • I.press — Shortcut for I.pressKey
  • I.pressEnter

We need new tools for testing the modern web.

Choose the right tool for the job

This post is an extension of my lightning talk at JSConf.Asia 2016:

A big thanks to the organisers of JSConf.Asia for having me on stage.

UI testing is CRITICAL.

Usability is important. It’s the main reason why your users stay or leave, no matter how innovative your underlying tech is. The user interface is often the first thing people see and complain about (and perhaps it is also the reason why many developers shy away from front-end work, but that’s a story for another day). I’ve seen many interesting applications fail simply because they did not handle their users gracefully and left them…

Shi Ling Tai

I used to kung-fu, now I code-foo. Dev'ing since jQuery days. CEO of UI-licious. Making the web a better place everyday.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store