Hi. My name is Kinoshitaand I act in the Eight section of Sansan. ``Eight`` is a free-to-use business card organizer and professional social networking program for soul, with over 2 million file users. I am the lead of the QA squad of Eight, and in this post I will talk about our experience adopting mabl this twelvemonth.

Creating tests without code in mabl

is an E2E test automation service for Web applications. It allows exploiter to create tests while enter actual operation using Chrome extensions, which makes it possible to create examination without coding. In add-on you can also implant created tests into CI/CD to incorporate them into the growing summons, run cross-browser tests, and schedule point tryout to run at a predefined escort and clip.

The need for automation

At Eight, we run regression tryout called `` pre-release check '' before releases. They run to ensure that the added and/or modified functionalities do not unexpectedly regard other functionality. We run these tests before every freeing. However, for Eight 's server-side and Web front-end updates, we were not able to run for every release because of a few key problem - there were too many items to reexamine in the pre-release cheque and the releases were delivered twice a week.

Too many items for the pre-release chit

Eight has various functionalities including managing business cards as well as SNS elements such as profiling and posting, to organization-level functionalities such as employ program and card sharing functionalities, all of which has increased the act of particular to check. To run adequate cross-browser examination manually postulate two to three full working days to complete.

Two regular releases present every week

Releases for Web aspects and server-side of Eight are delivered regularly twice a week. Running the above tests so frequently requires considerable test execution resources to run them. Under these circumstances, we have not been executing pre-release cheque on the Web side every time. We have been running pre-release checks only for liberation that would widely touch users, such as update source code and version-ups of Rails.

Even so, the problem with eminent spending costs on every run remains. They could be run by using a lot of manpower, however, it is inefficient to drop two to three workday for the same tests every single time - so we decided to automate them to acquire operational efficiency and run test for regular releases.

Why we prefer mabl

Pro tip: Tools like SUSA can handle this autonomously — upload your app and get results without writing a single test script.

1) Coding is not necessary

The principal reason we take mabl is that it does not postulate coding to create trial. There are test automation options that involve writing test code, like Selenium for instance, but it also requires manpower of engineers who can code to make and maintain tests. With a tool like mabl, the ability to make tests without coding liberates things from the above restriction so that anyone can create and maintain the test. This allows our team to allocate engineering manpower to developing new functionality and modifications.

2) Includes the power to test emails

You can likewise automate testing of email speech with the mabl Mailbox functionality. It can test whether an email can be delivered to the expected address, or whether the behavior of the links within the email are correct. The mabl Trainer can publish consecrate email address. Sending an email test to the address allows you to assure the UI and the links of the email on mabl Trainer.

3) Testing across web browsers

Many people look a mutual job with fixation testing - amend the efficiency of cross-browser examination. With mabl, the like tests can be run by selecting one or multiple browsers in a single detent. It is likewise potential to select whether to run multiple tests simultaneously in parallel or browser-by-browser (sequentially).

Additionally, mabl can run designated tests when a clout request is uploaded on Git by integrating mabl into your CI tool. I am happy with it because it can be use for various purposes in addition to pre-release checks.

Increased test coverage

Now with mabl we run tests before each release every week. The vantage of adopting mabl is that we can now run the tests that we did not get clip for, which has already yielded positive results by helping us detect fault that would have otherwise been difficult to identify.

*Special thanks to Kinoshita-sanfor sharing the Sansan story with our reader hither. Visit https: //buildersbox.corp-sansan.com/entry/2020/08/27/110000to say the original post in Japanese and follow their journey with test automation. & nbsp;

 

See for yourself how easygoing it is to create tests with mabl?Sign up for a free trial today.