Home / Companies / Sauce Labs / Blog / January 2014

January 2014 Summaries

3 posts from Sauce Labs

Filter
Month: Year:
Post Summaries Back to Blog
Here is a neutral and interesting summary of the provided text: Front-end testing with Webdriver has improved significantly in recent years, allowing developers to test complex UIs and web applications more effectively. With the rise of browsers like Chrome, it's now possible to write integration tests for specific flows, rather than relying on unit testing. To start writing front-end tests, developers can use tools like Chromedriver locally or in the cloud with Sauce Labs. By simulating user actions and testing flows, developers can ensure that their applications work as expected, even when working with complex DOM-heavy code. With Webdriver, it's possible to write comprehensive smoke tests that can be easily transferred into a CI environment, allowing for a test-first development approach.
Jan 28, 2014 761 words in the original blog post.
The new plugin allows users of JetBrains TeamCity to integrate their Sauce tests, enabling them to run and view test results within the TeamCity environment. The integration provides a seamless testing experience, including steps performed, screencast, and screenshots, all accessible through TeamCity. This integration aims to simplify the testing process for those using both platforms.
Jan 23, 2014 77 words in the original blog post.
Selenium WebDriver's PHP bindings have a limitation when it comes to remote file uploads. When running tests on a different machine than the test programs, the files specified for upload are not available to the browser. Selenium 2 solves this problem by providing a method to upload the file to the server and then giving the page the remote path of the file. This functionality is exposed in some language bindings but not in PHP, until it was added to Sausage, allowing for remote testing on Sauce Labs Selenium 2 Cloud. To facilitate remote testing, a function called `fileDetector` is used to determine if a string should be interpreted as the name of a file. If the function returns true, the system transparently reads the file, encodes it in Base64, and sends it to the Selenium server, putting the remote path into the file upload form element instead of the local one. This allows tests to proceed without trouble.
Jan 08, 2014 588 words in the original blog post.