McDonald's Big Mac Sauce is one of the most iconic fast-food condiments on the market. But aside from the chain temporarily selling dipping cups of the Thousand Island-like sauce earlier this year and giving away thousands of bottles back in 2017 ...

Ex-McDonald's Chef Claims You Can Find Big Mac Sauce At the Grocery Store

It’s always BBQ sauce season. And right now is a great chance to try new BBQ sauces, as families gather around tailgates across the nation for fall cookouts. While where you live used to dictate ...

Wow Your Tailgating Crew With These Amazing BBQ Sauce Recipes

Scientists doing “gain-of-function” research said that heightened fears of lab leaks are stalling studies that could thwart the next pandemic virus. By Benjamin Mueller and Sheryl Gay Stolberg ...

Lab Leak Fight Casts Chill Over Virology Research

There are 60 calories in a Mambo Sauce from McDonald's. Most of those calories come from carbohydrates (100%). To burn the 60 calories in a Mambo Sauce, you would have to run for 5 minutes or walk for 9 minutes. Let us know what you think! Review the ...

McDonald's Mambo Sauce Nutrition Facts

The New York Jets suffered a significant blow on defense, as Pro Bowl cornerback Sauce Gardner was ruled out Saturday with a concussion. The Jets will face the Philadelphia Eagles on Sunday ...

Jets rule out Sauce Gardner (concussion) for Eagles game

This will make Jets’ fans heads hurt. Late Saturday afternoon, the team ruled star cornerback Sauce Gardner out of their game with the Eagles on Sunday with a concussion. He joins fellow ...

Sauce Gardner ruled out for Eagles matchup with concussion in Jets injury catastrophe

Gardner (concussion) was ruled out for Sunday's contest against the Eagles. Gardner didn't participate in Friday's practice and had been listed as questionable for Week 6, but the Jets' decision ...

Jets' Sauce Gardner: Ruled out Sunday

McDonald's just debuted a new “Mambo” sauce, bringing a version of the popular D.C.- and Chicago-area sweet-and-spicy condiment to a national audience. (Jennifer Beeson Gregory/The Washington ...

McDonald’s mambo sauce is a tasty if largely token nod to Black America

You can’t quite say the same of Baja Blast Hot Sauce, a one-off hot sauce created in 2023 and flavored like the soda. It’s possible to still get Baja Blast Hot Sauce and try it, if you really ...

What is Baja Blast Hot Sauce? And how do I get it?

The owners — aka the “saucy scientists” — of My Sauce Lab know what they’re doing. Their curated collection of hot sauces doesn’t just add spice to a dish, but builds flavor with ...

My Sauce Lab

Sauce Labs

sauce-labs

Preparing the infrastructure is one of the most significant challenges in mobile test automation. It's an exciting engineering task to build a scalable and reliable environment with emulators or real devices. Previously I’ve shared my experience of creating in-house infrastructure in the topic . Mobile Infra from Scratch Own infrastructure has a lot of benefits, but if we are talking about huge scaling, it makes sense to think about cloud solutions. Among many providers, one of my favorites is Sauce Labs.  I like this service's ease of migration, ease of use, and runtime features. Usually, creating a new test session for for Appium tests looks like this: DesiredCapabilities capabilities = new DesiredCapabilities();
capabilities.setCapability(MobileCapabilityType.PLATFORM_NAME, "iOS");
capabilities.setCapability(MobileCapabilityType.PLATFORM_VERSION, "15.4");
capabilities.setCapability(MobileCapabilityType.DEVICE_NAME, "iPhone 13 Pro");
capabilities.setCapability(MobileCapabilityType.APP, APP_PATH);
driver = new IOSDriver(new URL(GRID_HOST), capabilities); WebDriver constructor requires remote server URL and capabilities. A remote server could be directly an Appium server or Grid connecting different devices or servers. To run tests on Sauce Labs, enough to replace the host of the in-house hub with a Sauce-managed hub and add some additional capabilities using . platform configurator Sauce-managed hub URL could be found on the “User Settings” page and usually looks like this: https://${user}:${access_key}@ondemand.eu-central-1.saucelabs.com:443/wd/hub The next is capabilities configuration. Follow Automated → Platform Configurator on left sidebar and get caps for needed environment: Here are present which are specific capabilities for Sauce Labs platform. They should be merged with general WebDriver capabilities that are typically used for your tests. souce:options MutableCapabilities sauceOptions = new MutableCapabilities();
sauceOptions.setCapability("appiumVersion", "1.22.3");
sauceOptions.setCapability("build", "<your build id>");
sauceOptions.setCapability("name", "<your test name>");
capabilities.setCapability("sauce:options", sauceOptions); You can find all needed options on page in the official documentation. Test Configuration Options So final code which creates a new session will look like: DesiredCapabilities capabilities = new DesiredCapabilities();

//Original options used before
capabilities.setCapability(MobileCapabilityType.PLATFORM_NAME, "iOS");
capabilities.setCapability(MobileCapabilityType.PLATFORM_VERSION, "15.4");
capabilities.setCapability(MobileCapabilityType.DEVICE_NAME, "iPhone 13 Simulator");
capabilities.setCapability(MobileCapabilityType.APP, APP_PATH);

//Sauce labs specific options
var sauceOptions = new MutableCapabilities();
sauceOptions.setCapability("appiumVersion", "1.22.3");
sauceOptions.setCapability("build", "001");
sauceOptions.setCapability("name", "My Awesome First Test");

//merging capabilities
capabilities.setCapability("sauce:options", sauceOptions);

driver = new IOSDriver(new URL(SAUSE_LABS_HOST), capabilities); After the session starts, you can find your test on the "Test Result" page by name and build number, which was provided in capabilities. One of the greatest features is the session's real-time view - click on test and follow into view. All information that could be helpful for reporting: logs, video, and screenshots is attached after the session is finished. What about working in a private network? A common case is when applications need to have access to the private network of your company, e.g. when you test the compatibility of an old app with a new back-end that is not in production. For this reason, you should use which starts in your network and creates a secure tunnel with Sauce infrastructure. This way the application runs in the Sauce cloud and connects to the internal network via this tunnel. Sauce Connect Proxy provides detailed instructions about setup and use. On “TUNNEL PROXIES” page you can find links to binaries and quick start command. Sauce Connect Proxy Quickstart Guide After a successful start, you receive a message in the console "Sauce connect is up.” This tunnel will be displayed on “TUNNEL PROXIES” with green mark. To use this tunnel, just add sauce-specific capability and put the tunnel name. After that, all traffic from the launched application will go through Sauce Connect Proxy. tunnelIdentifier sauceOptions.setCapability("tunnelIdentifier", "awesome_tunnel"); You may need additional tuning of traffic, so my advice is carefully read documentation. Sauce Connect Proxy E.g., a good way is to set concrete domains that should be proxied, and others go via the public internet to reduce proxy load and traffic amount. It can be done via or flag. -tunnel-domains -t Also, you might need set domains that do not require SSL resigning with flag. Requests from specified domains will not be re-encrypted. --no-ssl-bump-domain Conclusion Sauce Labs presents itself as the world’s most comprehensive Continuous Testing Cloud. It provides numerous combinations of OS/Browsers, mobile emulators & simulators, real devices and always-on scalable infrastructure. If you think about scaling your current testing processes and reducing infra-support operations, I think it’s a great choice. I hope this quick overview & guide will be helpful.

Migrating Appium Tests to Sauce Labs

“Will my job become obsolete as AI becomes more advanced?” This is a question that’s recently kept many professionals up at night. As artificial intelligence continues to spread its tentacles into various industries, many experts are warning about the pervasive reach of this development. “AI will wipe out a lot of current jobs, as has happened with all past technologies,” Lawrence Katz, a labor economist at Harvard, told the Guardian earlier this year. “But I have no reason to think that AI and robots won’t continue changing the mix of jobs. The question is: will the change in the mix of jobs exacerbate existing inequalities? Katz is one of many who believe rapid advancements in machine learning and robotics will kill numerous jobs, especially the repetitive and manual ones. Industries like manufacturing, customer service, content creation, and data entry are particularly vulnerable to automation. How Many Jobs WIll Be Lost to AI? According to Forbes, Goldman Sachs estimates that 300 million jobs could be lost or diminished by AI. In a 2019 study by Wells Fargo, researchers concluded robots could eliminate up to 200,000 jobs in banking alone in the next ten years. In May 2023, AI contributed to 3,900 job losses in the US, making it the 7th highest contributor to employment losses cited by employers that month. Other experts argue the sky is not falling because of AI and humans are still winning the job market. “I think people are able to adapt quite quickly, like when Photoshop came onto the scene a long time ago,” OpenAI CEO Sam Altman testified during a Senate panel hearing on AI. “For a while, people were quite fooled by Photoshop images but then pretty quickly developed an understanding that images might be Photoshopped. This will be like that but on steroids.” Other AI proponents hold a similar view: Every technological revolution, from the industrial to the digital, has raised similar fears, yet every time, the economy adapted, and new job roles emerged. The consensus is that AI will free humans from mundane tasks, giving them more time to focus on creative, strategic, and interpersonal roles that AI can’t perform quite well. “ChatGPT can’t design a system, or build an architecture, or create the ecosystem of supporting infrastructure you need for any complex system,” Marcus Merrell, the vice president of Technology Strategy at Sauce Labs, observes about OpenAI’s groundbreaking tool. “It can potentially help you think through some ideas, but it can’t innovate. Most importantly, you still need to know the difference between a good answer and a bad answer.” Each expert is right: AI’s impact isn’t merely binary – it’s not just about job creation or destruction. The crux lies in job transformation. While AI will reshape the professional landscape, our adaptability, foresight, and willingness to learn will truly determine our place in it. The same could be said about lightning channels. “Workers will require new skills as the division of labor between humans and machines continues to evolve,” the World Economic Forum advises. “It is critical that businesses take an active role in supporting their existing workforces through reskilling and upskilling, that individuals take a proactive approach to their lifelong learning, and that governments create an enabling environment to facilitate this workforce transformation. This is the key challenge of our time.” Will your job become obsolete? Possibly. Will you still thrive in this tech-driven era if you lose that job? It’s less about the job and more about how you evolve. This story was distributed as a release by Ascend under HackerNoon’s Brand As An Author Program. Learn more about the program here: https://business.hackernoon.com/brand-as-author

Will the Workforce Be Taken Over By AI?

কর্মশক্তি কি এআই দ্বারা নেওয়া হবে?

Wird die Belegschaft von KI übernommen?

¿La IA se hará cargo de la fuerza laboral?

La main-d’œuvre sera-t-elle prise en charge par l’IA ?

क्या कार्यबल पर AI का कब्ज़ा हो जाएगा?

労働力はAIに奪われるのか？

AI가 노동력을 장악할 것인가?

A força de trabalho será dominada pela IA?

Будет ли рабочая сила захвачена ИИ?

İşgücü yapay zeka tarafından ele geçirilecek mi?

Lực lượng lao động sẽ bị AI tiếp quản?

劳动力会被人工智能接管吗？

Test Faster, Test Smarter: Unlocking Selenium's Full Potential In today's fast-paced software development landscape, speed is of the essence. Testing teams strive to deliver high-quality software at a rapid pace, and plays a crucial role in achieving that goal. the execution time of UI test suites Selenium, the widely adopted UI testing framework, provides powerful capabilities for automating browser actions and validating web applications. However, is essential to ensure efficient testing processes and timely feedback. optimizing the execution time of Selenium test cases Explore five key strategies for accelerating Selenium test execution, along with the integration of Launchable's intelligent test optimization tools to further enhance speed and efficiency. 1. Efficient Selenium Locator Strategies Selenium Locators identify the correct UI element on a page, making it possible to create successful automation scripts. Optimizing your locator performance significantly reduces test execution time. Consider the following strategies: Utilize CSS selectors instead of XPath, as CSS selectors are generally faster and more efficient. driver.find_element(By.CSS_SELECTOR, "input#username") Employ unique and stable locators, such as IDs, names, or CSS classes, to ensure consistent test case execution. driver.find_element(By.ID, "username") Avoid excessive nesting of locators, as it can lead to slower element identification. driver.find_element(By.CSS_SELECTOR, "div.container input#username") For example, let's say you're automating a login functionality. Instead of using a complex XPath expression to locate the username input field, you can use a unique CSS selector, such as , resulting in faster test execution. input#username` 2. Test Case Prioritization and Parallel Execution To maximize test execution speed, it's crucial to prioritize test cases based on their business impact and implement parallel execution. Consider the following techniques: Identify high-impact test cases that cover critical functionality and prioritize their execution. Implement parallel execution using frameworks like TestNG or JUnit to execute multiple test cases concurrently. If you have a test suite containing multiple independent test cases, , reducing overall execution time. parallel execution can allow you to execute them simultaneously Get faster feedback without spending more on running parallel tests Launchable leverages AI to , generating dynamic test subsets. This approach enables teams to identify issues earlier while simultaneously minimizing compute costs. by adopting dynamic parallelization. predict which tests may fail 3. Make Your Selenium Testing Data-Driven Data-driven testing uses your test data to make your test execution more efficient and allows you to validate application behavior without running every test every time. Consider the following practices: Implement data-driven testing using Selenium and related frameworks, such as TestNG's data provider or JUnit's parameterized tests. Manage test data efficiently by using external data sources, such as CSV or Excel files. Make by leveraging Predictive Test Selection to optimize tests based on historical data patterns. Launchable builds a machine learning model based on your git data to get deep insights into how your tests run and how efficient they are. Selenium truly data-driven Then, it identifies what tests you should run, recommending the tests that directly test what was changed, . saving you time and speeding up your releases 4. Selenium Test Suite Optimization Optimizing the structure and content of your Selenium test suite can significantly reduce execution time. Consider the following optimization techniques: Identify and remove redundant test cases that cover similar scenarios. Reduce setup and teardown time by utilizing test fixtures and leveraging browser session reuse. Isolate and parallelize independent test cases to execute them concurrently, further speeding up the test suite execution. If your test suite includes multiple tests for user authentication, consider consolidating them into a single test case with parameterized inputs. To fully optimize your Selenium test suite, you need insights into the health of your tests and trends over time. like test runtime is crucial for improving development cycles, enabling faster feedback loops, and better test maintainability. Test runtime measurement brings various advantages, such as optimizing parallelization, managing resource allocation, prioritizing tests, and facilitating continuous improvement in your CI/CD pipelines. Measuring critical test health metrics Launchable's , enabling you to identify and optimize the test suite execution for maximum efficiency. Launchable provides automated tracking of test runtime, giving you in-depth visibility into the health of your test suite. This includes the ability to identify flaky tests, track the duration of test sessions, optimize the frequency of test sessions, and analyze the ratio of test session failures. Test Suite Insights provides valuable insights into test suite health KPIs 5. Selenium Test Environment Optimization Optimizing the test environment configuration contributes to faster test execution by making your environment run as smoothly as it possibly can. Consider the following strategies: Use lightweight browsers or headless modes, such as Headless Chrome or Firefox, to reduce resource consumption and improve performance. Using a headless browser eliminates the need to open a physical browser window, saving system resources and reducing overall execution time. from selenium.webdriver.chrome.options import Options

options = Options()

options.add_argument("--headless")

driver = webdriver.Chrome(options=options) Leverage cloud-based testing platforms, such as Selenium Grid or Sauce Labs, to distribute tests across multiple machines and browsers, increasing parallel execution capabilities. Ensure proper resource allocation and management, including CPU, memory, and network, to avoid performance bottlenecks. Reduce the need for context switching and streamline your test notifications where your developers are already working with Slack Test Notifications. Eliminate the need to hunt through inboxes or check in your CI; Launchable's and failures in the test environment, enabling swift action without disturbing your workday. personalized Slack Test Notifications provide real-time alerts about test execution performance Takeaways Optimizing Selenium test execution is paramount for efficient testing processes and timely feedback. By implementing these five strategies and , UI testing can significantly accelerate test execution, reduce development cycles, and deliver high-quality software with confidence. Achieve faster test execution times, optimize your testing workflow, and ensure high-quality releases in a time-efficient manner. integrating Launchable Also published . here

Speeding Up Selenium Test Execution: Five Ways for Quicker Feedback

Puppeteer vs Playwright vs Selenium vs Cypress The first thing you should start creating your framework with is choosing a browser interaction engine. It is the engine that will become the cornerstone of your tests in the future. Therefore, the choice of engine is the foundation of the house that you build (and then this foundation cannot be remade by third-party libraries). Chapter 1. Choosing an Engine At the moment, there are 4 popular ways to work with the browser: Selenium, Puppeteer, Cypress and Playwright. Below is a comparison table of these engines. Selenium Puppeteer Cypress Playwright Developer Google Microsoft Project started 2004 2012 2015 2020 Which browsers support Chrome, Firefo, Edge, Internet Explorer, Opera, Safari. Chrome-family browsers (Electron, new Edge). Chrome-family browsers (Electron, new Edge), Firefox. Chrome-family browsers (Electron, new Edge), Firefox, WebKit. Code All open source All open source There are paid tutorials All open source Programming language Java,Python,C#,Ruby,JavaScript. Java,Python,C#,Ruby,JavaScript. JavaScript,TypeScript. Java,Python,C#,JavaScript,TypeScript. Explicit network control No No Represents a context-wide network hook to stub and simulate network requests. Represents a context-wide network hook to stub and simulate network requests. Headless mode for browsers Not all drivers support headless mode. Supports headless mode. Supports headless mode. Supports headless mode. OS Need Mac for Safari and Windows for IE (Edge). Work on 3 platforms (Windows, Mac, Linux). Work on 3 platforms (Windows, Mac, Linux). Work on 3 platforms (Windows, Mac, Linux). Principle of operation In Selenium WebDriver you have three processes: 1)Selenium webdriver. 2)Browser driver such as ChromeDriver, GeckoDriver (for Firefox), EdgeDriver, SafariDriver, etc. 3)The browser itself. All the communications between these processes mean that Selenium tests take a long time. What is good about Puppeteer?It runs a headless browser and uses the DevTools protocol, so tests are faster and more stable compared to Selenium. The code you write in your Cypress test scripts doesn't run outside of the browser like it does in WebDriver. The browser launches it. In fact, it executes your test code and the code of the application you are testing. Tests written with Playwright run in a clean slate sandbox called browser contexts. Average execution time (in seconds) 3.66 2.22 10.35 3.19 Standard deviation (in seconds) 0.65 0.41 2.67 1.23 Chapter 2: How will we launch? Selenium Puppeteer Cypress Playwright OS Need Mac for Safari and Windows for IE (Edge). Work on 3 platforms (Windows, Mac, Linux). Work on 3 platforms (Windows, Mac, Linux). Work on 3 platforms (Windows, Mac, Linux). You yourself create an agent (machine) with the desired OS and run tests on it. The agent can be a local computer. The first way to run tests is to create an agent and run tests on it. Agents We have to create two agents, one is Windows, the other is Mac (if we want to use Safari and IE browsers) You can create only one agent (Windows, macOS, Linux). You can create only one agent (Windows, macOS, Linux). You can create only one agent (Windows, macOS, Linux). Running in parallel on different browsers. We have to use the Selenium grid if we have different browsers. Just run. Just run. Just run. Connecting to a third-party server with browsers and using them to run autotests. The second way: cloud service. What are there? A lot of servers support Selenium. There are definitely BrowserStack and Sauce Labs and TestingBot. There are definitely BrowserStack and Sauce Labs and TestingBot. There are definitely Sauce Labs and TestingBot (in theory, it supports remote connection. Do I need to pay? Yes Yes Yes Yes Summary: If testing on IE or genuine Safari is very important to you, Selenium is the only one for you - it's a centuries-old, time-tested product. If you have chosen Selenium, then I advise you to use cloud servers. Otherwise, all the work to update WebDriver and the browser will fall on your shoulders. If cross-browser compatibility is important to you, but you refused to support IE (it will cease to be supported in 2021-2022), and you also agree to the WebKit engine instead of Safari, then feel free to take Playwright. This is a fairly young product, but rapidly developing. It's better, of course, to keep your own agent because it will be cheap (you can buy a headless Linux agent). Browser updates go inside the Playwright package. In fact, these browsers may not be installed on the machine, they run from the Playwright box. If cross-browser compatibility is not important to you and you can run tests on one browser, then take Puppeteer. It is the fastest, and also chromium, at the moment, the most stable browser. If it is important for you to do Network mocking in tests, then use Cypress, there are more ready-made scripts than on Playwright. But! This solution is only suitable for those who are friends with JS. Chapter 3: What's Next? Select Test Runners. The next steps after choosing an Engine should be the step of choosing Test Runners. A framework that will organize your tests. Test runners depend on the programming language you are writing in. For JS, you can compare the 3 most popular ones: Jest, Mocha and Jasmine. In automation, I did not notice much difference in the use of one or another runner, but I still note one point: Two popular contenders are Jest and Mocha. Jest is an open source testing framework developed by Facebook. Built into the popular create-react-app package, it's faster and more convenient for writing idiomatic JavaScript tests. It has built-in simulation and assertion capabilities when running tests in parallel, which provides a smoother and faster test run. One of the unique features of Jest is that it provides snapshot testing for complete control over the user interface. Mocha provides developers with a basic testing environment with options such as assertion, mocking, and spy libraries. It is one of the most flexible JavaScript testing libraries. A small disadvantage of Mocha is the need for additional configuration. Chai, the most popular open source assertion library, is used with Mocha Epilogue Wrapper The third stage of preparation for automation should be the choice of a framework - a wrapper for the engine. For example WebdriverIO (for Selenium) or CodeceptJS (for Selenium or Puppeteer). The choice of wrapper should also be made by weighing the pros and cons. This is a topic for the next article. Among other things, there are also visual frameworks. The most popular are Percy and Applitools. They will add a beautiful screenshot comparison to your application if you need it. The Cypress and Playwright engines can be used without additional wrappers, they have excellent descriptions of the functions. Selenium and Puppeteer should always be wrapped so as not to reinvent the wheel.

The 4 Pillars Of Automation

I have spent the last years working at DevOps-focused companies, so the topic of product-led growth (PLG) is near and dear to my heart, as are the topics of finding your first steps into PLG. Understanding user needs, translating those into experiments, and learning from and refining usage patterns are the activities I like to spend my day on. After joining Quali earlier this year, I have had the opportunity to explore a higher ratio of self-serve signups and interactions through , Quali’s SaaS product aimed to service DevOps and IT professionals, becoming an excellent candidate to implement PLG techniques. Torque Our first steps into PLG were largely guided by our formal users, friends, and prospects. We are following the to discover and validate our findings. Here are some of the meaningful focus areas we have addressed so far: continuous discovery method Ease of sign up A significant portion of our users would use Github as a repository for their Infrastructure-as-Code (IaC) components (Terraform, Helm charts, Ansible scripts, etc.), which are reused at scale through Torque. Previously, users had to enter their credentials to join the service. Recognizing that many users already have their identity defined in GitHub, we figured many would benefit from an accelerated sign-up/login experience. We strongly believe that with more usage and number of users of our solution, the more we can deliver value and optimize our product. Therefore, we want to encourage users to use the product a lot! Why wouldn’t we want the small businesses or those just testing us to experience the goodness we provide? Therefore, we offered a feature-equivalent freemium, where small businesses can leverage us from the get-go and avoid growth blockers down the road. It was important for us to offer a feature-equivalent experience so that DevOps architects testing us would know exactly what their experience would look like once they start using the solution. No surprises, no smoke and mirrors. Accelerated onboarding experience Much has been said about reducing the “clicks-to-Aha moment”, asking for information only when necessary and clearly in return for value. Prior to the recent change in the UI, a first-time logged-in user would go through two pages of questions and then about five steps to start working. No “Aha moment” in sight. We realized that’s a non-starter, and the numbers talked (more on that next). Our new onboarding experience is split into three phases: Pre “Aha” moment (AKA “see the value for yourself”): 1-click to launch a predefined environment and see it in action (we initially shot for more steps but got down to one). “Aha moment”: Three steps to connect your cloud and launch your own environment (AKA, this is working for me, and it was easy!) Ongoing experience: connect your CI (API integration), design blueprints, etc. Daily work. Learning from real-world usage This sounds trivial; however, it’s anything but. Our assumptions and hypotheses will live and die by our understanding of user behavior. We track the critical steps and selections in the portal. We enable the entire team to utilize a standard reporting tool to create funnels and other dashboards, and we are now able to see a different behavior for the changes we deployed recently. While planning, deploying and analyzing is the role of every product manager on the team, one of them took leadership in orchestrating the usage patterns tracking, and now it’s a part of every feature we introduce. We are now moving into a new rhythm of looking at the various PLG tools and how each applies to our user journeys in or outside the portal. We are prioritizing experiments, defining success criteria for each (user behavior), deploying, measuring and refining. Rinse and repeat. Next, we are planning to look further at some focus areas. One of those pertains to email communications to newly-signed users. We’re considering both event- and time-based series to engage the user with guidance and encouragement. Additionally, we’re looking at optimizing the journey to the “Aha moment”. Can we accelerate while demonstrating the goodness we’re doing behind the scenes? We believe we can. So, Quali is on the PLG bandwagon, with all the hype and commitment. I also wanted to give thanks to one of my biggest PLG mentors, Chris Zappala, VP of product and growth at Cypress, for many moments of PLG learning and realization. We will be sure to learn and improve. There is no better feeling than seeing usage patterns shift as an outcome of an experiment. Amir Rozenberg is the VP of Product at Quali, a global leader in infrastructure automation solutions with a deep background in testing and QA solutions. Amir and his team are obsessed with helping users and companies accelerate their software delivery cycles by removing complex infrastructure blockers and creating an efficient, scalable and predictable. Prior to Quali, Amir served as a product leader at Sauce Labs, driving key transformative initiatives such as low code testing and mobile test automation. Before Sauce Labs, Amir led a set of offerings for Perfecto, a world leader in automated testing for mobile and web apps, where he enabled accelerated application innovation while maintaining high-quality standards. Amir holds a Bachelor of Engineering (EE) degree from Tel Aviv University. About Amir Rozenberg

Using a Product-Led Growth Mindset to Improve User Experience

Zalenium is a container-based Selenium Grid featuring video recording, live preview, rudimentary authentication, and a dashboard. The integration of Docker and Kubernetes makes Zalenium an appealing choice for setting up Selenium-based infrastructure. Why Zalenium is a great choice to manage the selenium Grid? Selenium Grid consists of "Hub" and "Nodes". Nodes are the configurations that we want to test, such as Windows 10 with Chrome. We use RemoteWebDriver to point our tests to the HUB, which then routes them to the appropriate Node if one is available or queues them. It's always difficult to set up a selenium grid with nodes since you need to know how many nodes to set up.  If there are too few nodes, your tests will begin to time out, and you will need to add more nodes. A large number of nodes causes a waste of machine resources.  Another challenge is to maintain nodes and keep up with the latest browser versions. How does it sound to have a scalable and dynamic grid that adds nodes as needed and disposes them after the test is finished? Introducing Zalenium - Selenium Grid extension which scales your local grid dynamically with docker containers to run tests in Firefox or Chrome. You can also redirect your tests to cloud grids like Sauce Labs, BrowserStack, TestingBot, CrossBrowser Testing, LambdaTest. Let's try Zalenium: 1. Install on your  system (if not already have yet) Dockerdesktop https://docs.docker.com/docker-for-windows/install/ 2. Check docker installation using the command: docker -v 3. Pull below docker images by using these commands: docker pull elgalu/seleniumdocker pull dosel/zalenium 4. Check the docker image by using the  command: docker images 5. Run Zalenium by below command on cmd: docker run --rm -ti --name zalenium -p 4444:4444 -v /var/run/docker.sock:/var/run/docker.sock -v /tmp/videos:/home/seluser/videos --privileged dosel/zalenium start 6. After successfully running the previous commands, check if containers are up: docker ps 7. Now you can access below URL’s Grid console – Zalenium Live Preview – Dashboard – after running your first test http://localhost:4444/grid/console http://localhost:4444/grid/admin/live http://localhost:4444/dashboard/ 8. Run the selenium script by modifying the code as below: 9. You can watch the application running live by Zalenium live Preview: 10. After execution you can view the video of the test from the Zalenium Dashboard: Find out more under complete documentation: https://opensource.zalando.com/zalenium/ Also published by Tahera Firdose. here

Getting Started with Zalenium: Docker-based Selenuim Grid

Cross-browser testing is crucial as it helps us discover how our app or site performs across various legacy and modern websites. As of May 2021, the global browser market share report by states that around 64.73% consume content via Google Chrome, followed by Safari at 18.43%. StatCounter People across the world consume content via different browsers and on different devices, and to ensure our site performs uniformly across various browsers, we perform cross-browser testing. Picture Credit: BrowserStack But, here's the thing — it's not always enough to perform just cross-browser testing. Some scenarios require cross-browser testing from different geo-locations. If our apps or website personalize based on the location, for instance. language, currency, etc. — we've got to test our product across various geo-locations. It’s important to note that some sites display cookie alerts based on locations, and even search results are customized based on geo-location. Since these features might reflect differently across different geo-locations — we must perform cross-browser testing across different geo-locations. This also gives us a clear picture of how our product appears in different countries. Now that we've understood the importance of cross-browser testing across various locations, let's explore the tools of the trade or the testing tools that'll help us perform cross-browser testing. Apart from validating the cross-browser functionalities, these tools will also help us check the overall UI of our site too. Testsigma: Testsigma is a cloud-based test automation tool that supports cross-browser testing from different geo-locations and it comes with thousands of real devices with various OS and browser combinations. Apart from that, we can integrate Testsigma with any cloud-based device labs like Hybrid, Sauce Labs, BrowserStack, etc. It’s a cloud-based tool so, it can be accessed from any location, any time and it doesn’t require any set-up time either — a pro-point for remote teams. Besides, Testsigma is empowered by AI to auto-heal in case of minor changes and to detect corresponding affected resources. In Testsigma, we can set up geo-location in desired capabilities to perform geolocation-based testing. This tool supports a bunch of locations that we can effortlessly choose while setting up to run the tests. To know how to test your website in various locations using Testsigma, check out this . article Features i. Supports CI/CD integration ii. As it's cloud-based, you can scale it up or down based on the project requirement; this is cost-effective as we pay for what we use. iii. We can set up geo-location on a real device or GPS to perform geolocation-based testing. iv. To perform tests, you can choose screen resolutions and devices on the tool itself. v. Bugs are captured via screenshots and logs; this is reported through email, Slack, Teams, etc. vi. Tests can be executed parallelly in multiple environments. Price: $99 upwards (for startups), enterprise solutions involve $249 monthly if billed annually. At the moment, Testsigma has a 30-day free trial. Sign up . here BrowserStack: BrowserStack is a test automation tool that comes with around 2,000 desktop browsers in its cloud. This tool supports real-time debugging and permits running tests on internal dev and staging environments, behind firewalls, etc. Using this test automation tool, we can test from any location using its geo-targeting feature. From checking how our site is performing SEO-wise to geo-tagging, it offers a bunch of features. Picture Credit: BrowserStack Features i. Supports CI/CD integrations ii. Testing design layouts is simple as it comes with a screenshot generation feature. iii. Supports testing on a range of screen resolutions, for instance, 800×600 to 2048×1536. iv. It's cloud-based v. Its native browser experience ensures test results are as accurate as the tests we perform on local browsers. vi. Supports parallel testing and you can perform various Selenium Webdriver tests simultaneously across various browser, device and OS combinations. vii. Tests can be run by setting up a real device to any GPS location. Price: $29 upwards monthly, if billed annually Geo Screenshot: Geo Screenshot is a pretty versatile tool for performing cross-browser testing from different geo-locations. This tool lets us test UI, language, currency, and local search rankings for a website. If our product requires multilingual translations — Geo Screenshot can help us tap into that too. Plus, we can check what content or geo-targeted ads are pushed in those locations. Picture Credit: Geo Screenshot Features i. Supports CI/CD integrations. ii. Offers emulators and user agents for you to mimic real devices for testing. iii. It’s fully web-based and does not require any additional configurations or set-ups. iv. Screenshot comparison to check how the site looks across various locations. v. Geoscreenshot supports testing across multiple resolutions. vi. It’s possible to test and compare several results at the same time. Price: $19 for a basic plan : CrossBrowser Testing CrossBrowser Testing is an online automation testing tool by Smart Bear, and it supports manual and live testing on over 2,000 browsers and real mobile devices. We can check the look and feel of the site/app across various geo-locations and this tool also gives us insights on what sort of ads are being pushed on our site based on the location. It also offers native browser debugging tools and consoles. Picture Credit: CrossBrowser Testing Features i. Supports CI/CD integrations. ii. Takes screenshots, logs across multiple browsers or devices. iii. It’s cloud-based and offers access to Mozilla Firefox’s earliest browsers such as 12, 13. iv. Supports screenshot comparison for quick bug fixes. v. Supports parallel test execution. vi. Offers access to Automation tests can be run using various frameworks like Appium, Selenium, etc. vii. Offers a proxy lab in its Local Connection to perform geo-location tests. Price: It's $39 upwards monthly for live testing; $169 for unlimited testing. GeoPeeker: GeoPeeker is an online tool that lets us view how our website appears in various geo-locations. This tool renders the appearance across locations on the same page so we can perform a side-by-side comparison of our site's UI. Using this tool, we can choose the locations and screen resolutions that we want to run tests on. Another important feature is if the site is down in our location, this tool is helpful in discovering other locations where it's down. Picture Credit: GeoPeeker Features i. GeoPeeker lets us pick and assign screen resolutions, manifest delay, user-agent settings, and peek locations for testing. ii. It’s a web-based tool and requires no additional setups or configuration. iii. Generates screenshots for quick comparison. iv. Offers insights on the ping timings on our website across various geo-locations. v. Supports parallel geo-testing across various locations. Price: It begins at $9 monthly These are the top cross-browser testing tools for testing from across different geo-locations. Which one caught your interest? Let us know in community.

Top Cross-Browser Testing Tools to Test from Different Geo-Locations

Quality Sense Podcast with Tristan Lombard: The Power of Community Building 

*Illustration by Regex SEO This article is a part of “Dear Developer, Make Your Life Easier” series. You can read one of the latest installments, the “ Top 10 Browser Console Hacks ” here . We’ve all been browsing on our phone or tablet and found a website that didn’t fit on our mobile screen and no amount of device rotation or screen manipulation would make it work. It’s frustrating when you’re trying to use a site that isn’t responsive to the type of device you’re using, when the browser console is full of errors, and nothing works the way it’s supposed to. In our world of instant gratification, . Users will just move on to the next search result and that traffic will be lost forever. no one sticks around on a non-responsive website As a website owner, it’s critical that your site is fully operational across not only multiple browsers, such as Chrome, Edge, and Safari, but that it also works effectively on all types of devices, including desktop, tablet, mobile, and more. Since mobile devices are constantly getting bigger screens, better resolutions, and releasing updates — that can affect how your site is displayed. Ensuring that your website displays and functions correctly isn’t a one-time test after launch; it’s something you’ll need to be checking regularly to ensure you aren’t losing hard-earned traffic due to problems with how a browser displays your site. Between is now done on mobile devices, so it’s critical to ensure your site works effectively across all types of devices. But how can you test against the huge number of mobile devices on the market, with new ones being released all the time? 70 to 80 percent of all web browsing Luckily, you don’t have to buy one of every type of web-capable device on the market to test your website’s effectiveness across different browsers and devices. You can use a browser testing tool. A browser testing tool, or browser emulator, will help you test website performance across multiple browsers and see if any errors appear or if any features aren’t functioning correctly, and ensure the design is displaying correctly and responsive across all browsers. Just as there are a lot of devices and browsers available, there are also a lot of tools for testing those browsers. Here are the top tools for testing your website on mobile devices. BrowserStack BrowserStack is more than a browser emulator. It allows you to test your website across more than 2,000 real devices and browsers all in one place. While some emulators focus on a certain type of device or browser, BrowserStack was built to provide results on all varieties of browsers and devices, including Android and iOS devices. It also allows you to run tests automatically, so you don’t have to do all the work manually. It can also help you locate the source of coding problems, to make finding a fix much faster. There is a cost for the service, depending on how many features you want and how many tests you want to run at a time. While BrowserStack is probably more advanced than what a business with a single website needs, it offers amazing insights to those who need to be monitoring website performance in various browsers. Other available programs with features similar to BrowserStack include: CrossBrowserTesting by SmartBear, LambdaTest, Browserling, Experitest, Functionize, and Sauce Labs. All of these are paid services that provide testing across a huge array of devices to ensure your website is always functioning correctly. ScreenFly ScreenFly is essentially the opposite of BrowserStack’s feature-rich offerings. ScreenFly is a back-to-basics online tool that allows you to see how your website looks on a variety of screens. You can check how the display appears on more than 30 popular devices, including televisions, Kindle devices, desktops, mobile phones, and tablets. While ScreenFly won’t help you breakdown where any problems are occurring, it’s an easy, and free, way to quickly check your site’s display and functionality on an array of popular devices. Plus, it’s very simple to use and will give you a good understanding of how your site appears on some of the most-used devices. Appetize.io If your digital footprint includes an app, in addition to your website, you’ll need an environment for testing that as well. Appetize.io allows you to test your mobile app on any device, regardless of the platform. So, if you’re working on an iOS app, but only have access to a PC, you can still test your app using Appetize.io. You’ll be able to mimic real-world conditions and debug problems quickly. If users are reporting problems from specific devices, you can quickly test the issue and get a fix out fast. This is a paid software, but it includes a free version for one user. Most importantly, it has all the features you need to ensure your app is operating seamlessly and offering your customers the best possible experience. Given the speed at which web technology is evolving, ongoing testing and monitoring of websites and mobile apps must become a non-negotiable part of your marketing strategy. Nothing wastes marketing dollars faster than directing users to a non-responsive website, and regular testing is the best way to ensure users are getting a quality experience on your site. Shameless Plug If you are not sure what causes your website to misbehave, take advantage of free website audit — we will find the issues in no time. Regex SEO Comments? This article is purely an opinion based on my work experience. If you had bad experiences with emulators I have cited, and have a better option, leave a comment below!

Top Mobile Browser Emulators: Developer's Humble Opinion

Cloud computing has revolutionized IT since the 2000’s, and this revolution is far from over. Formerly, organizations would host their data on-premise as that was the only option available, but with the advancement in technology, and fast-changing business demands, cloud-based solutions started turning out to be a more flexible and powerful option for organizations. There is a mass migration underway to adopt cloud infrastructure and avoid the hassles and operational costs of managing infrastructure in-house. Migration to the cloud is a long, phased-out journey rather than a one-time ‘set it and forget it’ task. Netflix, one of the pioneers in cloud computing, to completely migrate from on-prem to cloud. It’s reasonable to say that less savvy organizations and more entrenched ones will take even longer. In fact, a complete migration may not even be a possibility for many organizations, and most will likely end up with hybrid cloud setups. took 8 years Having a well-planned can be a crucial factor in the success of an organization. The major reason for cloud-adoption failing is a wrong adoption strategy, and issues that crop up during the migration. One simple example could be the false belief that if an application is running on any platform (say Windows) under certain conditions, it would work equally well on a public cloud instance with the same configuration of Windows. The ‘works-on-my-machine’ issue plagues many an application. cloud migration strategy Developing a cloud migration strategy is not a straightforward path and involves several challenges. In this post, we discuss seven key steps to a winning cloud migration strategy. 1. Start by taking an honest look at your team’s expertise The best place to start your cloud migration journey is with your team’s technical expertise. This includes the kind of programming languages used to build applications, what kind of infrastructure it takes to run the applications, how many hands are on board (Dev, QA, Ops), how frequently releases happen, and how mature the team is in terms of adopting agile methodologies like DevOps. Ideally, you want to keep the best parts of what’s working for your teams and leave behind outdated processes as you move to the cloud. Cloud migration requires training for various teams so they can adapt to the operational and design principles of the cloud. You may prefer to hire an external consultant who has walked various organizations through successful cloud migrations already. This will minimize the risk of failure. 2. Employ a hybrid approach Taking a page from the Netflix example, it is good practice to start small and go further into the cloud than make the jump all at once. Especially when dealing with large applications or workloads there are too many things that can go wrong. In this case, it makes sense to adopt a hybrid approach where only specific elements of the large application are migrated to a cloud environment and much of the app runs on-premise as it always has. The biggest benefit of this is that it makes the transition seamless. You can test the compatibility and identify any gaps and loopholes in specific parts of the system. With some applications, you can use the ‘lift and shift’ model, but with others, you may need to completely refactor or rearchitect them to adapt to a cloud environment. In some cases, the entire application need not be migrated to the cloud ever. For example, in a financial services organization, for compliance purposes, critical data needs to be stored on-premise or on a dedicated cloud instance that the organization has full control over. Here, hybrid will be the default approach and not just a temporary one. Create a checklist of key elements to be migrated to the cloud as well as the timing and resources required for each of them. This will keep you focused on the right things throughout the migration process. 3. Gauge security & performance risks One of the biggest reasons for not wanting to migrate to the cloud is the perceived risks that come with it. Public cloud services like AWS EC2 run applications of multiple organizations on shared servers. While this doesn’t present security risks, it can at times result in performance issues, or downtime if the cloud vendor’s services themselves fail. Migration to a public cloud platform may also involve the risk of compromising data security. All it takes is an open S3 bucket to leave all your data exposed to hackers. When working with the cloud there are cloud-specific security tools that automatically scan for vulnerabilities and report on them. Critical data needs to be backed up. This isn’t difficult with the cloud as storage costs are relatively cheap. Cloud backup services can help you keep data on standby so your app can weather downtimes and outages. 4. Go all-in with containers, microservices, and DevOps The cloud calls for a fundamental change in how your teams operate. Taking the old waterfall development methodology, and monolithic application architectures with you to the cloud is a recipe for disaster. Instead, the cloud calls for decomposing applications into distributed microservices that are run on container-based architecture. These microservice applications are built following the . This involves a fundamental shift in mindset and operations, but it’s what will deliver the full benefits of the cloud. By starting small and making a gradual change over time you’ll see that these approaches complement each other. Soon, these cloud-native approaches will become the new normal, and you’ll wonder how you ever functioned without them before. DevOps methodology 5. Take testing to the cloud Cloud applications can’t be tested using non-cloud testing approaches. Most modern applications run in a browser and their performance across various versions of browsers should be tested. Spinning up each version of a browser on a physical system is tedious and not worth the effort. On the other hand, using a Selenium-based browser testing solution like Sauce Labs is the way to go. These modern testing tools are cloud-based. This means you upload your test script and execute the test in an online interface. The results of the tests are delivered in an online dashboard. Not just browsers, you’ll need to test performance on various mobile devices which can be even more complex. Look for a testing solution that can execute the kind of tests you need to run, and do them at scale. 6. Gain end-to-end visibility with monitoring and logging It is an old saying that “you can’t manage what you don’t measure”. When it comes to the cloud you’ll need a mix of monitoring tools to gain an end-to-end view of your system. Cloud providers provide proprietary monitoring tools which are tightly integrated with their cloud platform, but their features are limited. You may want to consider a standalone monitoring tool to monitor events, logs, and setup alerting for when things go wrong. Open source tools like Prometheus and the ELK stack have raised the bar when it comes to monitoring cloud-native applications. Commercial solutions have kept pace and innovated so that there are numerous options to monitor cloud applications and gain a single pane of glass view. 7. Keep costs in mind Though cost is the last point we’ll cover here, it is likely the first thing on the mind of your CFO or business leader. The factors that decide the cost of a cloud migration include data storage, processing power, tools for testing and monitoring, and the security-related services. Other important factors are the cost of implementing and integrating cloud apps, and the cost to train teams on cloud technologies. Select an optimum cloud platform which fits your budget, without making any compromise with the performance. Further, spread out your expenses so that you can prioritize the important ones early, and leave luxuries for later. Conclusion Successful migration to the cloud not only brings down the cost of running applications but also enables modern capabilities that are not possible with an on-premise setup. The cloud migration strategies mentioned here will ensure your journey to the cloud is secure, seamless, and successful.

Stories, News & Mentions about SAUCE-LABS

Sauce-labs’s Stories on HackerNoon

Sauce-labs's News & Mentions