5 reasons to choose Screenster over your current UI testing automation tool

Looking for an efficient codeless solution for UI testing automation? Meet Screenster, a new cloud-based platform that brings speed and simplicity to UI testing. Here are five reasons why we’re different from (and better than 😉) our competition. 1. Super-short learning curve with no coding skills required Okay, we all know that every other UI testing automation tool boasts having a smooth learning curve. Here’s why Screenster is different: when we say our platform is easy to pick up, we mean it. Screenster requires, precisely, zero programming skills. Instead of relying on scripted tests, the functionality of this platform revolves around record-playback and screenshot comparison. This allows manual QAs and product owners to cover the whole UI and test actual UX scenarios instead of hand-coding verifications. Now isn’t this what UI testing automation is all about? When working on Screenster, we’ve put a lot of effort into making it accessible to non-testers. You don’t need to read manuals to automate basic UI tests, and most of the things are easy enough to learn while actually working with the platform. 2. Maintainable tests created in 3 minutes … And I’m not talking about all those “hello, world!” mock tests. Take a... More

12 features that every UI testing automation tool must have

What software do you use for UI testing automation? For that matter, how did you come to choose the solution that you’re currently using? Making lists is always handy, so let’s do exactly that. Below, you will find a list of requirements that we deem must-have for every modern tool used for automated user interface testing. When working on it, we’ve used the feedback from our customers — and from our competitors as well. Besides, the checklist below pretty much mirrors our roadmap for Screenster, our very own platform for UI testing automation. Without further ado, read on. 1. Speed Higher speed equals higher ROI. This is why it’s paramount that the solution you’re using for UI testing automation allows you to quickly create, edit and debug your suites. So if creating a basic test suite takes more than 30 minutes, you should probably start looking for another tool. 2. Codeless UI tests Don’t get me wrong, coding is fun — but we think the real fun is to code features, not tests. And let’s face it, there’s really no such thing as a robust suite of hand-coded UI tests that covers the whole user interface, not just its separate... More

The Rise of Automated Testing Platforms

It’s 2017, and software testing is as important than ever — so is choosing the right automated testing platform. So how do you make the right choice given the number of available automated software testing tools? In a sense, testing software features is like shipping goods. Your clients don’t care about what means of transportation you used to ship the product — as long as it gets there in time. You, however, will definitely want to make sure you’re using a vehicle that delivers goods in time, in pristine condition, and at the right cost. Just for fun, let’s stick with the shipment analogy and examine both paid and open source automation testing tools for web applications. Horse (Manual Testing) If you’re shipping something small and time isn’t a priority, you can hand your package to a guy on a horse. This sort of logistics is as reliable as the delivery guy, but it’s simple to implement. Need to ship more? Hire a couple more horsemen. Just like horse transportation, manual testing works fine as long as your product is small. But once things get bigger, testing manually becomes costly and time-consuming, so it’s not sustainable in the long run.... More

Why is manual regression testing still happening in 2017?

Where does manual regression testing fit in the software testing process? In fact, does it even make sense to test software manually, given the sheer number of automated regression testing tools available? I bet you’ve seen people ask similar questions on StackOverflow — as well as a good dozen of articles exploring the topic. So why would you need another post on the same topic? Well, here’s a reason to put my two cents into this same ole discussion. The choice between automation and manual regression testing looks simple on paper. Most manual regression testing tutorials will tell you that the complexity of manual testing grows exponentially as your project scales. Automated tests, on the other hand, help you move faster than manual tests, they reduce the chance of human error, and they are more cost-efficient in the long run. So, on paper, you should always strive to automate everything you can, right? After all, you can always have your developers write unit and API tests, and hire a QA team for everything else... In theory, yes, that’s how things are supposed to work. In real life, however, things get more complicated. The more so if we are talking about... More

Are TDD and automated UI testing compatible?

Image credit: SoapUI Test-driven development is awesome — unless you’re dealing with UI testing automation. Sure, test-driven UI development is technically possible, but TDD isn’t exactly ideal for situations requiring full functional tests, and full functional tests are indispensable to UI testing. For this reason, using TDD for UI border on overengineering. Choose this path, and you’ll end up working with mock objects or project object models (POM), adding new layers of complexity to your project. And in many cases, you won’t be able to tell if doing this will pay off. Besides, the way UI testing automation is done in real-life projects another problem. In real life, UIs — and web UIs in particular — undergo a lot of tweaking. No matter how well-specked your UI is, once you do a UI prototype and play around with it, changes are always coming. So how do people do UI testing automation in a TDD project? The short answer is they don’t. What they do instead is clearly separate concerns between the UI and the underlying logic with MVC, MVP, MVVM, or similar architectural patterns. Basically, the main idea here is to keep the UI logic minimal so it's mostly a... More

UI automation testing with Smart Locators

When it comes to UI test automation for web projects, element locators can become one hell of an issue. But is there anything you can do about it? The thing is, poorly-written locators are just a part of the problem. Writing good locators is, in fact, not that difficult. After all, good locators are merely a matter of either accessing IDs or building robust CSS or XPath selectors. And you can always get your developers to throw in a couple of extra IDs, right? Actually, there’s a whole bunch of other factors to consider. Once these factors come into play, UI test automation turns into a challenge for any QA specialist, no matter how experienced. Let’s look at a couple of scenarios to see what factors can affect the work of your QA team. Scenario 1. Throwing in extra IDs Let’s start with something we all can agree on. An ID-based locator is the best option for 100% of UI test automation cases. But in real life, developers will not put IDs on every element upfront, and any data-driven content (e.g. a table) will have repeated elements that cannot have unique IDs anyway. In cases like this, path-dependant locators will... More

Automation testing of Gmail UI

Are you overloaded with web UI regression testing and finding that manual visual testing is a pain? You definitely need some automation testing tool and guess what: we have just the thing for you! Skeptical about tools abilities to handle complex sites that use not just plain HTML, Web 1.0-styled pages? You should be, because most of them suck at it :-)  Let me demonstrate you how I built UI regression testing automation process for Gmail inbox (let us imagine we are developing new Google Mail UI) in 15 minutes. My objective was to get unwanted changes highlighted as bugs while leaving out any types of expected behavior. When a new email is received, the correct behavior for an email UI is: New mail gets added to the inbox Sender’s ID or signature are displayed next to the email Date and time is displayed for sent and received mail Alert icons (like the “!” sign) displayed on tabs where new items appear Such UI changes are expected and an automation testing tool should identify them correctly. But since a human-like AI still remains far from being officially released anywhere, we could be content with a tool that ensures that expected changes... More

QA automation for Ajax UI tools: testing AjaxSwing with Screenster

AjaxSwing automatically converts Java desktop applications to web applications. It was the first product built by our company and is still the only platform capable of automatically running Java Swing apps on mobile devices running iOS and Android. For the first 10 years (10 YEARS PEOPLE!) we were struggling with changes to AjaxSwing because we could never truly understand the effects of each code change. We wanted to automate the UI regression testing with Selenium and tried a few other alternatives, but since none were testing the page visually these tools failed to detect broken CSS and HTML formatting. Touching anything in Java or CSS code was like walking on a minefield with delayed explosions but real pain. Screenster, a visual regression testing tool gets into action! We have now been running pain-free with Screenster as part of our CI. We use it for visual testing, CSS testing and most of the functional testing. Given that Screenster ensures pixel-perfect regression testing, our developers are now fearless. We've built over 50 tests that go over common scenarios, and with TDD we keep adding new tests every week. Every time our CI catches visual differences of a few pixels, cropped borders or... More

Screenster Roadmap: more regression testing features, better UX

Screenster team has big plans for the future and many fresh ideas of improving the process of visual regression testing. This roadmap includes what we are working on and what we want to accomplish. Release 1.1 Target date: Summer 2016 Suites that allow to organize tests into a group Copy/Paste for suite, test and test step Concurrent test execution URL override for running tests against a different environment UX updates for easier navigation Command sets that group test steps automatically for faster execution   Release 1.2 Target date: Fall 2016 Environments with parameters and baselines Smart approve to baseline across multiple tests and steps   Release 1.3 Target date: Winter 2017 Execution on the cloud Internet Explorer support Versioning of tests Branching/Merging of tests Verification modes: text only, nothing [raw] Want to try Screenster on the cloud? Try Online [/raw]

Screenster 1.0 is released! UI regression testing made simple

We have FINALLY released the 1.0 version of Screenster! It’s been a long road but we had to make sure we have a product that works. Screenster is now ready for basic and smoke testing and there is a ton of new features on the way. All of the core features are now working: Visual baseline with changes approval Record/playback of visual tests Ignore regions for dynamic UI Smart dates handling Extend/parameterize tests Smart locators with auto-maintenance Jenkins integration and REST API We are already working on version 1.1 It will have the following cool new features Concurrent test execution Copy/paste everywhere Simplified URL overriding Improved UX Download Screenster server and let us know what you think! [raw] Want to try Screenster on the cloud? Try Online [/raw]
WordPress Image Lightbox Plugin