Five Blogs – 8 December 2022

The (best) five blogs we can read today. Check them out. What Were You Thinking? Written by: Frank Sonnenberg Why Putting Profit Over People is Always Bad for Your Company Written by: Lolly Daska How Visibility on Software Supply Chain Can Reduce Cyberattacks Written by: Priya James Leading With “I Want To Apologize” Written by: Terri Klass The Motivational Leader Written by: Steve Keating Quote of the day: “And one has to understand that braveness is not the absence of fear but rather the strength to keep on going forward despite the fear” -Paulo Coelho You can follow this page on Twitter

Fresh Tester Start In A Project

Subscribe to my YouTube channel: https://www.youtube.com/@STQTalks When I started working in Software Testing, the amount of information that I needed to grasp was exhaustive. Not only that I needed to learn about the industry, the business, the domain,  the product and its features, I had to get acquainted with the testing side of things – testing strategy, methodologies, test setups, tools required, etc. A very exciting challenge indeed, but it could also lead to burnout quickly if not properly handled. It’s worthwhile to have a charter or a map on learning and to gain knowledge. In this blog, let us look at the top priority things as a fresh tester start that needs to be considered in their journey to get accustomed with their day-to-day work in their project. Product Requirements Analysis The first and foremost thing that a fresh tester needs to look into is the product they are working on, and how it fits into the industry, the business, and the domain. Studies have shown that 65% of the defects found are related to requirements. In order to come up with requirements that are complete in several aspects like performance, security, accessibility, UI/UX, etc., it is important to first understand the product’s placement in the business. We should not be looking at the requirements in isolation, but should look at the fulfilment of customers’/end-users’ needs from the industry/domain/business perspective and validate whether the product fulfils those needs. It would also be worthwhile to compare the requirements with other[…]

The One Mistake People Make About Time Management

Do you sometimes feel overwhelmed?That there’s just too much to do and too little of you?Have you ever gone online to search for time management?I know I have — countless times.Photo by Elisa Ventur on UnsplashEarlier in my career, I often looked for a hack or a tweak that would change everything.I never found that thing. I just wasted more time browsing for a solution.Then a tweet got me angryTime Management is nothing but your attempt to change how you FEEL.“That’s some new age mumbo jumbo. I’m looking for hardcore tools to manage my stuff!” I told myself.Yet I noticed that some people were outstanding in time management without apparent tools. And I wanted to figure out how.So I started asking around.Finally, I asked the CEO of one booming business here in Finland. “I want to find a perfect tool for time management,” I told him. “How do you manage your time?”He returned with an innocent question, “Why is it important for you to find a time management tool?”“To get my stuff and to-do’s sorted out,” I replied.“Now, why is it important to you to get stuff and to-do’s sorted out?” he got curious.“So I could get more time for myself and still get my job done,” I said.“Ok. Why is it important to you to get more time for yourself?” the CEO pushed.“To be able to do more things I love with the people I care about,” I replied“Now we’re talkin’,” he said. “Why is it important to you to do more things you love?”“To feel that I’m living for myself. To feel that I’m[…]

I am Speaking @ LeadDev Webinar Panel – Dec 14th

I am super glad to announce that I have been invited by the LeadDev team as a Panel speaker in the upcoming Webinar on “Building a better Testing culture” The webinar will be held on 14th December at 10.15 PM IST. Details for registration can be found here https://leaddev.com/events/building-better-testing-culture I am thrilled to be a […]

First impressions of test automation with Playwright

I have recently automated some tests using Playwright. It is a free-to-use Node.js library created by Microsoft that is designed to be used to automate end-to-end testing.  Playwright supports chromium, WebKit and Firefox, and, by default, all tests are run on all three browsers. Tests can be run in headless mode. It supports, Java, .Net, JavaScript, TypeScript and Python. I am writing my tests in TypeScript and have used FrontendMasters TypeScript Fundamentals, v3 course to help me get up to speed with TypeScript.  Its first-party test runner is Playwright Test, although a number of test runners such as Jest\Jasmine and mocha can be used. Playwright Test feels familiar because it has describe blocks skip and other familiar functionality. There are good resources for learning Playwright, which include free courses provided by both LambdaTest and Test Automation University. One of Playwright’s strengths is its support for iframes. Playwright contains functionality that enables tests to interact with elements inside an iframe, giving it an advantage over many test automation frameworks. To explore how to test elements inside an iframe you can use Jonathan Thompson‘s blog post about how to use Playwrights support for iframes[1]. You can use `frame.getAttribute` and `frame.$$` to get the values of attributes in elements within an iframe, which helped my test automation. It is really helpful that you can wait for events inside an iframe, for example with frame.waitForFunction(). Playwright has good easy-to-use documentation, however, you may not find what you are looking for. If you can’t find[…]

Five Blogs – 7 December 2022

The (best) five blogs we can read today. Check them out. How Great Leaders Communicate Written by: Carmine Gallo ‘Black Panthers’ – A SIM Swap Gang Connected With Dark Web Got Arrested Written by: Balaji N What doesn’t Google have a QA department Written by: kt.team What is the Optimum Software Developer to Software Tester Ratio Written by: TestBytes The Best Time to Test Your App Written by: Dennis Martinez Quote of the day: “When you don’t share your problems, you resent hearing the problems of other people.” -Chuck Palahniuk You can follow this page on Twitter

How to Write an API Tester Resume (With Example)

API Testing Resume: In this video, we will learn How to Write an API Tester Resume with examples shared. Learn API Testing from Scratch: In this video, we are covering the How You can learn the API Testing Manually and API Automation with 150+ Videos ... Read more The post How to Write an API Tester Resume (With Example) appeared first on Software Testing & Automation.

Why You will Never Feel Ready For a Job Interview

Software Testing Interview: In this video, I will discuss how to topic Will you ever feel ready for a job interview? and why You will Never Feel Ready for a job Interview. ✅ Visit below for LIVE Classes https://thetestingacademy.com ✅ Mastering API Testing using POSTMAN ... Read more The post Why You will Never Feel Ready For a Job Interview appeared first on Software Testing & Automation.

How to sort java streams

During one of the tests, I got a list of items sorted via an api. At least that’s what I thought. From that list, I always extracted the first item because it was always the most recent one that was in the database. One day, some of the tests started failing. It turned out that the first element was no longer the latest one. Since some of my test cases were based on this latest record, tests failed as a result. The solution is simple. I need to sort that list. In the test code, that list was not a List but a Stream. It turned out that it was not that simple as I first thought it was. How to sort a stream Suppose you have a class of Members and they contain a name and an age. Now I would like to have a stream of Members and I want to sort that stream by age. Since the age is a number, sorting is easy. Some java code: import java.util.*; import java.util.stream.*; class Test { static class Member { private String name; private int age; public Member(String name, int age) { this.name = name; this.age = age; } public String getName() { return name; } public void setName(String name){ this.name = name; } public int getAge() { return age; } public void setAge(int age){ this.age = age; } @Override public String toString(){ return "Member{name='" + name + "', age=" + age + "}"; } } public static void[…]

There is such a thing as testing that is not exploratory

The team had been on a core practice of clarifying with tests for a while, and they invited an outsider to join their usual meeting routine.Looking around, there were 8 people in a call. The one in charge of inviting the meeting shared their screen, for what was about to be their routine of test design sessions. He copied the user story they had been assigned to work on into the Jira ticket he had open, and called the group for ideas of tests. People started mentioning things that could be tried, and the one in charge wrote things down as the rest of the group watched. For a high level idea, he called for the detailed steps. Every idea that came about was written down and detailed. After the meeting, the group would split the work to automate it all. And two weeks later, they had all these tests passing, and a feature that just did not work.The magic glue they miss is what I call exploratory testing. The sense of caring for results in testing by focusing on learning and recognising that the time most people create test cases like above, it is the time when they know the least.You can add exploratory testing on top of this.You can lighten up the details you want to write to start with to leave more room for exploratory testing, where output of your testing is the documentation. You can seek to optimize for learning, being aware of the time used.The team that follows the[…]

Christmas Gifts For Software Testers

Its that time again folks! You guessed it – panic buying festive presents time! Need some inspiration on what to buy for loved one or colleague who works in Quality Engineering(QE)/Quality Assurance (QA) that will arrive in time for Christmas? Here are my top tips:- Books There have been several stellar software testing books released this year. Available digitally (hello last minute.com) or in good old fashioned paper form, they will give the software tester in your life something to do over the Christmas holidays once the standard family arguments are out of the way Testing Web APIs – Mark Winteringham (April 2022) The Complete Software Tester – Kristin Jackvony (August 2022) The API First Transformation – Kin Lane (December 2022) images of front covers of the software testing books mentioned Memberships Often, us testers aren’t fortunate enough to work for an organisation with a huge personal training budget. So we miss out on anything that requires a subscription or paywall, which can make finding decent content a bit more tricky. Want to help? Buy a monthly/annual Ministry Of Testing Pro Subscription Pluralsight monthly/annual learning platform subscription Udemy monthly/annual learning platform subscription screenshot from MoT website with reasons to go Pro Other bits Of course, most testers just want regular nice things for Christmas (if they celebrate Christmas at all that is). But if you want to get something more generic, or even give them the choice of something to get that’s still thoughtful, maybe a voucher could do the[…]

What is the difference between RUM (Real User Monitoring) vs. Synthetic monitoring?

The main difference between RUM and synthetic monitoring is that RUM involves tracking the performance of a website or application as experienced by real users, while synthetic monitoring involves using simulated traffic to test performance

What is RUM (Real User Monitoring) and how it helps in performance testing?

Real User Monitoring (RUM) is a method of monitoring the performance of a website or web application as experienced by actual users. This type of monitoring involves tracking various metrics, such as page load times, server response times, and JavaScript execution times, from the perspective of the user's web browser.

Five Blogs – 6 December 2022

The (best) five blogs we can read today. Check them out. The Value of Old Systems Written by: TuxCare Why Managers Matter Written by: Michael McKinney Preparing for a Russian cyber offensive against Ukraine this winter Written by: Clint Watts The best user story! Written by: Bhagya Perera E2E testing manifesto Written by: Victor Slavchev Quote of the day: “What seems like a reasonable distance to one person may feel too far to somebody else” -Haruki Murakami You can follow this page on Twitter

Tips to reduce flakiness in UI Automation Scripting.

There are a few steps you can take to reduce flakiness in UI automation scripting: Make sure your test environment is stable and consistent. This means ensuring that the operating system, browsers, and any other tools or applications are up to date and configured properly Use explicit waits rather than implicit waits. Implicit waits tell […]

Testing: From Aristotelian to Galilean, Part 2

In this post I’ll continue on directly from part 1 where we ended up with a lot of models and a recognition of competing interpretations of quality along with a need for testability. I should note that this post likely provides the culmination of all the “History and Science” posts up to this point. The goal throughout this series of posts was showing a bit of how testing had to develop so that everyone could understand the historical basis of how testing evolved within the context of the scientific method. Creating Increasingly Complicated Systems There’s a key lesson that people, like astronomers and other thinkers, were starting to learn as they got closer to actually doing science. With all of our models, we can increase complexity. Not a problem. Well, as long as our testing methods are able to keep up with that complexity. And our testing methods must be capable of being related to observations that have value. But, ideally, not just value in how something works but also in terms of how the way something works aligns with our experiences. And maybe a little about why it all works the way it does to provide the experience it does. Let’s head back to Copernicus and dig into a little more history along the same lines as we looked at in the previous post. It wasn’t just Copernicus that found circle for orbits didn’t always work so great. Those early Greek astronomers that Copernicus was responding to also recognized[…]

Remembering Jerry Weinberg: Weinberg on Writing – The Fieldstone Method

It’s been four years since – sadly – Gerald M. “Jerry” Weinberg passed away. Ever since then, I struggled with some public mourning about him, until recently I had just the right idea. On a weekly basis, I will publish a review of a book I read that Jerry either wrote himself or is about some of his work. With not so many books from Jerry left on my shelf, I picked Weinberg on Writing – The Fieldstone Method, published by Dorset House in 2006. As the title notes, Jerry wrote over 40 books in his career, spanning at least from 1958, up until his death in 2018. So, when such an accomplished author writes a book about writing, it’s a must-read in the case are considering writing on your own. I recall how Jerry made early on a distinguishment between an author and a writer, but I can’t find that reference in the book’s index. So it might as well have been a blog entry he published on one of his blogs at the time. Basically, an author could be a one-time contributor to a book or an article, while a writer makes a living from his writing work. The subtitle of his book can be explained rather simply, and Jerry offers his explanation from the get-go. A fieldstone wall is built with stones lying around in the wild. These are not perfectly shaped. So, if you want to build something like a wall out of fieldstones, you need[…]

Jokes and Poetry from a Stochastic Parrot

Tell a joke about a programmer and a tester attempting to enter Heaven and having to confess their sins.Two programmers were on their way to Heaven and they came to a fork in the road. One path led to Heaven, the other to Hell. The programmer who had been a tester in life said, "I'm not taking any chances. I'm going to test both paths to see which one is safe." The programmer who had been a developer in life said, "You fool! We don't have time for that. We need to take one path and trust that it leads to Heaven." The tester replied, "Trust, but verify."Another!A programmer and a tester were standing at the Gates of Heaven, waiting to confess their sins. The programmer went first and said, "I wrote code that I knew was buggy and released it anyway." The tester said, "I found the bugs in that code and didn't report them." The Gates of Heaven opened, and the programmer was welcomed inside. The tester was shocked and asked, "Why was he allowed in and not me?" The gatekeeper replied, "We already have plenty of bugs in Heaven. What we need are more testers."More.A programmer and a tester were arguing about whether it was better to be a programmer or a tester. The programmer said, "Programmers are the ones who create the software that makes the world go round. Without us, there would be no progress or innovation." The tester replied, "That may be true, but[…]

My first ever Advent of Code!