Lint Roller? I Barely Know Her
ellievsbear
wallacepolsom
@theartofmadeline
★
styofa doing anything
Today's Document
No title available
TVSTRANGERTHINGS
Keni
Claire Keane
Misplaced Lens Cap
PR's Tumblrdome
No title available
ojovivo
Andulka
tumblr dot com
h
2025 on Tumblr: Trends That Defined the Year
AnasAbdin
seen from United States
seen from Türkiye
seen from United States
seen from United States
seen from United States
seen from United States
seen from Germany
seen from Malaysia
seen from Austria
seen from United States
seen from Germany
seen from United States
seen from Russia
seen from Austria
seen from United States
seen from United States
seen from United States
seen from Germany
seen from United States
seen from United States
@browserup-blog
New Post has been published on BrowserUp
New Post has been published on http://browserup.com/post-ideas/
Post ideas
– Every error code and meaning during load/performance testing
– A master table with all error code and meanings summary linking to the other pages
– All major browsermob proxy errors
– Examples of each thing you could do with browserup proxy
– Performance Assertions
– Network Assertions
New Post has been published on browserup blog
New Post has been published on http://browserup.com/blog/brotli-support-in-the-browserupbrowsermob-proxy/
Brotli Support in the BrowserUp/BrowserMob Proxy
We are happy to announce Brotli support in the BrowserUp Proxy. The BrowserUp proxy is our fork of the BrowserMob proxy.
Brotli is an open source compression scheme by Google that offers superior compression capabilities over GZIP, the most popular alternative. At present, if you load either Google or Facebook, you’ll get web pages sent to you with Brotli compression. Previously, the proxy would ignore the content of text in Brotli (br) encoded pages.
Many sites are moving or have already moved to Brotli, and for good reason. Take a look at how much Brotli compression will reduce the size of your content. If you’re interested in better web performance, Brotli compression is something you should look at.
Along with Brotli support, we added in a couple other community PR’s, like a fix for Basic Auth credentials leaks in the proxy, and support for JSON content types with versions in the name into the new version. Give it a try!
<!-- if(wpa2a)wpa2a.script_load(); //-->
New Post has been published on browserup blog
New Post has been published on http://browserup.com/blog/browserup-proxy-release-1-1/
BrowserUp Proxy Release 1.1
We recently released version 1.1 of the BrowserUp Proxy. BrowserUp Proxy is a free utility to watch, test, and manipulate web application network traffic and performance.
The BrowserUp proxy is based on a fork of the BrowserMob Proxy, an open source project which hasn’t had a release in a few years. It uses the same API as BrowserMob Proxy’s REST API. It should work as a drop in replacement if you’re using the older BrowserMob Client Libraries We’re excited to build, add to it, and make it our own.
Our new point release features:
ZIP distribution with launch scripts, SSL certificates and keys
Dependency updates
New Post has been published on browserup blog
New Post has been published on http://browserup.com/blog/announcement-an-actively-maintained-fork-of-the-browsermob-proxy/
Announcement: An actively maintained fork of the BrowserMob Proxy!
We are pleased to announce our new fork of the BrowserMob Proxy, renamed the BrowserUp Proxy. The BrowserMob Proxy played a vital role in the Selenium testing ecosystem by allowing access to network request data, but it has unfortunately not been updated for a couple years.
The commercial load testing and monitoring company which maintained the project, BrowserMob, was acquired by a company named Neustar, and while the proxy had some great community support for a while, the main fork hasn’t been updated since 2016. As an example of how this poses a problem, HTTP2 support has been needed sorely and is still missing from the proxy. Additionally, it would not compile against Java 11.
We have no relationship to BrowserMob or their acquirer. We do have a love of real browser testing and browsers, though. Since we are planning to put a lot of effort into the proxy, we decided to brand this fork under our own name, BrowserUp.
What are our plans for the BrowserUp Proxy? HTTP2 support, which you can see now. Bug fixes. Websocket support. Modern dependency updates. Apache 2.0 license like it has always had. And… a lot of crazy new features that we will announce soon! Hint: Some are already done and can be found on the repo.
New Post has been published on browserup blog
New Post has been published on http://browserup.com/blog/coming-soon-free-open-source-selenium-power-tool/
Coming soon... Free open source Selenium power tool!
We’ve been working feverishly and, frankly, ignoring social media to focus on developing cool stuff.
At the moment, we’re working on open sourcing one of our creations–a Java-based Selenium super-driver. We should have something out within the month.
The BrowserUp SuperDriver simplifies the creation of clean firefox and chrome profiles for headless selenium web browsing. It should largely be a drop-in replacement for the standard Selenium Drivers.
But wait, there’s more! Performance assertions, databanking, networking assertions… and more! Join our mailing list and be the first to try it!
<!-- if(wpa2a)wpa2a.script_load(); //-->
New Post has been published on browserup blog
New Post has been published on http://browserup.com/blog/types-of-web-application-load-tests/
Types of Web Application Load Tests
There are a number of different common types of load tests. They each serve different purposes, and vet different capabilities.
Real-World Concurrency Test
A Real-World Concurrency test simulates normal production-like usage and determines the application’s scalability. This test is probably the single most important test for vetting a site’s capabilities.
Purpose: Vets the application for a certain number of users with production-like traffic and verifies performance characteristics.
Detects: Bottlenecks, issues including inadequate web server connections, CPU, memory, keepalives, inefficient queries and algorithms, load-balancer issues, worker thread/process issues, database connections, query problems and more.
Stress Test
A Stress Test verifies the websites capabilities when pushed passed expected capacity.
Purpose: Determine upper limit of system capacity and the next expected bottleneck.
Detects: Website breaking point, website degradation profile under increasing load.
Failover Stress Test
A Failover Stress Test verfies website performance when resources are taken away and recovered.
Purpose: Determine how failover conditions are handled including reduced web server, app server and database offlining, as well as recovery from changes in these conditions.
Detects: Correct behavior in the face of reduced capabilities, load balancing, automated recovery, error handling.
Endurance Test
An Endurance Test, also known as a soak test, involves testing a system with typical production load for a longer period of use.
Purpose: Verify the application can handle extended usage without resource scarcity issues.
Detects: Resource utilization problems over time where usage of a finite resources is exhausted over time. Typical problems include memory leaks, file handle leaks, database connection recycling, unrolled log files absorbing all disk space.
Bandwidth Test
A Bandwidth Test verifies the amount of bandwidth that your web server tier can pass. This test uses a large image hosted on your web server (not a CDN!) to determine the throughput your website can push through. A Bandwidth Test verifies the promised bandwidth can be delivered given your current configuration. By running an isolated bandwidth test, other tests may be safely run without downloading assets like images so long as the implied bandwidth requirements of those tests is within your established bandwidth-ceiling.
Purpose: Verifies your web server and networking capabilities in isolation.
Detects: Limitations with web hosting providers, network misconfiguration, load balancers, web server, and connection problems.
Baseline Test
A Baseline Test verifies website performance under a minimal-traffic scenario.
Purpose: This test determines best-case performance measurements for page load times.
Detects: Best-case page load time. Issues in testing scripts themselves.
Home Page Test
A home page test is a simple test that can verify some basic scalability issues.
Purpose: For static websites, this single-page test provides a decent estimate of a website’s capabilities. For true web applications, a home page test provides fast feedback on some problems.
Detects: Issues on a website’s homepage, as well as common web server issues and some configuration issues.
New Post has been published on browserup blog
New Post has been published on http://browserup.com/blog/website-testing-qa-link-roundup/
Website Testing QA Link Roundup
Here is a roundup of a few QA testing-related links we’ve picked up in our travels.
40+ Free software testing e-books
Big list of naughty strings for testing input data
Google Testing Blog: Just say No to more end-to-end Tests
Top Browser Extensions For Testing Software – Ministry of Testing
Is QA Dead? — ThoughtWorks Featured Insights
For REST requests and #testing, we love with Postman. Especially the sharing features.
Enjoy!
New Post has been published on browserup blog
New Post has been published on http://browserup.com/blog/load-testing-survey/
Quick Load Testing Survey
We’ve put together a new load testing survey. If you have a moment, we’d love to hear from you, and would greatly appreciate your feedback!
>> Take our quick survey >>
New Post has been published on browserup blog
New Post has been published on http://browserup.com/blog/announcing-our-load-test-scripting-series/
Announcing Our Load Test Scripting Series
We’re starting a Load Test Scripting series where we’ll cover common areas of site functionality, how to properly script them, and considerations for each type of script. We’ll be focusing on common functionality like authentication, product search, purchase, chat, and more. The posts will be tool-agnostic and focus on doing things right rather than any particular vendors or tools.
Our first post on testing your site’s authentication (login/logout capacity) is up already. We’ll add a link to each area below as we post them.
Scripting for Load Tests
How to Script Authentication Functionality
Keep an eye out for more from us–join our mailing list or subscribe to our RSS feed to keep in touch.
New Post has been published on browserup blog
New Post has been published on http://browserup.com/blog/estimating-concurrent-users-for-load-testing-with-google-analytics/
Estimating Concurrent Users for Load Testing With Google Analytics
When load testing, one of the first questions to figure out is how many concurrent users your testing should target for your real-world concurrency tests. Developing an estimate of your site’s maximum concurrent users provides a starting point for defining future performance goals. For a new site, this can be a challenge, but for an existing site, there are many sources of data you can work from to understand your site’s performance target.
If you know how to parse server logs, or have access to someone who can, the most accurate way to determine out your maximum concurrent users is probably to parse the log entries or use a log viewer to figure this out. You can also use Splunk to calculate this number if you’re a Splunk user. Here’s an example.
But, often times a ballpark number is good enough. For that, Google Analytics works just fine.
Peak Concurrent Users
First, let’s look at your peak concurrent users. If you are using Google Analytics, jot down your average session duration. This thumbnail graph can be found on the main dashboard.
Next, select a full year in the date-selector at the top. Find your heaviest during the year. Select that day and look at the hourly numbers and find the hour with the heaviest traffic and jot down how many users that is.
Session Windows in an Hour
Let’s figure out the proportion of sessions per hour. Assuming a 6 minute session length, this looks like this:
(60 minutes / 6 minute average session length) = 10 sessions per hour
Concurrency
Now let’s take the traffic for our busiest hour and work out how much of that falls into each session-sized window.
4000 hourly users / 10 sessions per hour = 400 concurrent users
That’s pretty good, but those users are not evenly distributed across the busiest hour. We’re really planning for the busiest minute in the hour, because if we undershoot and can’t handle the full weight of the traffic, people arriving during peak traffic could be deprived of our website!
Account for Some Variance
So we need to make allowance for the uneven-ness of traffic during that hour. For our fudge-factor, we’ll say 2x to account for the uneven spread. Based on what we usually see, 1.5x is typical, but 2x is safer. So 1/10 of the hourly load is 400, and we’ll use 800 as our number to ensure we’ve accounted for variance and we know we’re covered.
This concurrent users number provides a starting point from which to reason about your performance goals.
Future-proofing
In physical engineering, engineers plan for 3x the listed max capacity. So an elevator expected to carry a maximum of 3,000 pounds will be tested to 9,000 pounds. If you are growing, 3x or greater might make sense. So remember that this base number is a starting point, and we should scale our goals up or down, as appropriate to the business objectives, targets, and SLA for your website.
New Post has been published on browserup blog
New Post has been published on http://browserup.com/blog/how-to-create-a-login-script-for-load-testing/
How to Create a Login Script for Load Testing
Scalability-wise, authentication is one of the most critical functions in a web application. Why? For most non-trivial web applications, the majority of their functionality requires prior authentication. The implication here is that the scalability of the system’s authentication provides a hard-ceiling on your website’s scalability. If your users can’t login, they can’t get to your website’s other functionality.
What is an authentication script in the load/performance testing world? Very simply, it is a targeted script that logs in and logs out of your web application. The authentication script is used to simulate a portion of the load the application experiences during normal usage.
Testing a website’s authentication performance correctly can be challenging. What are the key considerations in an authentication script?
Isolation
To isolate authentication functionality, a login script should touch as few other pages as possible. If any extraneous pages are included, they should be chosen to be the least impactful from a resource perspective. It is common for web applications to redirect to the last page a user was on before they logged in. In this case, the page should be a fairly simple page, with as little on-page business logic or database calls as possible.
On the same token, scripts other than the login script should touch the login functionality as seldomly as possible, and should not be logging in and out with each iteration. Scripts that login and out on each iteration overweight and overstress the authentication components.
Isolating the authentication functionality achieves several things
The scalability of the authentication components can be tested and tuned directly.
The proportional load on the components can be tuned proportionately for real-world scenarios.
False negatives due to overstressing authentication components can be avoided.
For many sites, the login script (in pseudocode) is simply
visit /login post credentials to /login, verify landing page is in authenticated state visit /logout verify page is in unauthenticated state
Verification
An authentication script should verify that the landing page post-login is in an authenticated state–as opposed to displaying an error, or remaining unauthenticated. The easiest way to accomplish this for most sites is to check the rendered HTML for the username if it is displayed. This isn’t always possible, but provides a quick and easy check. Alternately, check for content that is only present when a user is authenticated.
Additionally, after logging out, the post-logout page should be checked to confirm the username is absent.
Databanking and Caching
At the application-level, applications often cache recent users. Because of this, to make an authentication script’s load characteristics realistic, it needs to authenticate with many different users. So when creating a login/logout script, it must be databanked (aka data-driven) with enough records to simulate normal usage and prevent the application from surviving off cached records, which would skew your results with an overly positive performance result.
New Post has been published on browserup blog
New Post has been published on http://browserup.com/blog/real-browser-testing-selenium-link-round-up/
Real Browser Testing (Selenium) Link Round-up
Here are some interesting links we found on real browser automated testing:
Having Selenium wait for a page to load after a click can be tricky. Here’s a good way to do it.
PhantomJS vs. Selenium comparison by Phantom’s author.
7 things you need to know to make Selenium tests reliable and maintainable.
Write up of page objects pattern in Selenium.
Automating an HTML 5 Range element in Selenium. Is this the best we can do?
Best Free Selenium training tutorials.
How to Use TestNG Annotations in Selenium (with Examples)
New Post has been published on browserup blog
New Post has been published on http://browserup.com/blog/whats-our-blog-about/
What's our blog about?
We plan to blog extensively on testing, performance and scalability related topics. Our content will include how-tos for creating testing scripts, performance testing and performance tuning. Our focus will cover QA, DevOps, and development of scalable websites from a development perspective.
We’ll be doing periodic link roundups of the content we post on the browserup twitter account. Follow us on twitter if you would like more frequent, lighter-weight performance related content.
We think performance testing and tuning shouldn’t be a dark art.