Back here for another week. As I mentioned last week, if you would like FfF in your mailbox every week, you can sign up here. The sign-up process feels a bit wonky to me, and I think my early subscribers may be spam bots, but ymmv. Also note that I’m still learning how to use the wordpress plugin I installed to send newsletters, so feedback is appreciated as I continue to tweak. Here’s some stuff I found interesting or worth sharing this week. Given my love of Radical Candor – I pre-ordered Kim Scott’s latest book – Just Work: Get Sh*t Done, Fast & Fair I’ve started to take inventory of the different personality and strength tests I’ve taken. I’ve done MBTI, Insights, Strength Finders, and probably a few others. Two of my favorites are The Working Genius (which I mentioned a few FfFs ago, and one called the Kolbe test – it’s less known, but pretty interesting. Here are my results from when I took it a few years back.This ‘Day in the Life’ post from the Netflix tech blog is really interesting. At least I think so.I found this article on being a senior engineer – or better put, and article on how to get shit done when you have to influence people. It’s 3 years old, but still worth watching.Why I hate the web lesson 137. HTTPWTF Thanks for reading – see you next week. (potentially) related posts: Five for Friday – February 26, 2021 Five for[…]
5.03.2021 | 11:57 קרא עוד...In this video, we are going to learn about the Test Plan, Do you really need a Test Plan Or Not ? ✅ Download Mind Map – https://sdet.live/3GKb ✅ What is Test Plan? A Test Plan is a detailed document that describes the test strategy, objectives, ... Read moreTest Plan : Is It Mandatory to Create Test Plan? The post Test Plan : Is It Mandatory to Create Test Plan? appeared first on Software Testing & Automation.
5.03.2021 | 10:28 קרא עוד...
You can find them everywhere. Hiding among church congregations, lurking in village halls, appearing suddenly at rehearsals, and ever-present in offices around the world. No one gave them this role, and it might not be a job that they want to be doing. Nonetheless, they’ve been here forever and won’t be going away any time soon. I speak not of cleaners, mice or even lawyers. No, I refer to the amateur AV engineer (aka audiovisual engineer).
What’s an amateur AV engineer?
I’m talking about the people who advance the slides, tweak the sound system or connect the laptop to the projector. The quiet teenager who jumps up to fix a crackling speaker. The village hall volunteer who paid attention to the sound technician’s explanation of the new sound system. The overworked minister who brings his own equipment to under-equipped churches. The funeral attendee – my wife – who hurriedly crafted a Spotify playlist and plugged their phone in when the undertaker had forgotten to bring the right CD. It’s not quite a thankless task, but it’s often something that people notice only when things have gone wrong.
The amateur AV engineer probably doesn’t have any real expertise. Rather, they’re the least unqualified person who happens to be in the room at any given moment.
My experiences as a reluctant AV engineer
I know very little about sound engineering, but I know enough to produce a result that is just about acceptable. I know what to touch (or not touch!) on[…]
The (best) five blogs we can read today. Check them out. How the Best Leaders Build Trust at Work Written by: Lolly Daskal Why You Should Be More Proactive and Less Reactive, and How to Do So Written by: Francisco Sáez Forget SOLID. Say Hello To SHOC Principles for Modular Design. Written by: Jason Gorman Why Testers Will Have Their Place In Software Teams Written by: Venkat Ramakrishnan Who is the Customer? Written by: Bill Wake Quote of the day: “Failure we can do alone. Success always takes help.” -Thomas Fuller You can follow this page on Twitter
4.03.2021 | 11:25 קרא עוד...
I like to read. I’ve always liked to read. As a kid I’ve read a lot. From picture books to comics, from science fiction to encyclopedias for kids.
Podcasts
According to my blog, I’ve been listening to podcasts since 2006. I used to listen to a lot of podcasts. I’ve moved to audio books in the last few years, but I’m still listening to a couple of podcasts that I really like.
Audible
In 2015 I’ve stumbled upon Audible and audio books. Since then, I’ve started to listen less podcasts and more audio books. Since then I listen to about 30 to 40 hours of audio books each month. That’s about an hour a day.
Goodreads
In 2016, I’ve found Goodreads. It’s a social network for people that like to read books. In Books That Have Changed My Life I’ve created a table with some Goodreads statistics. I’ve updated it to include the books I’ve read this year.
Year
Books
2016
68
2017
178
2018
90
2019
112
2020
208
2021
21
What Is a Book?
Before I start with the statistics, I have to define what I mean by a book. I will consider a book anything that Goodreads thinks is a book. Including picture books and audio books, even some podcasts. I’ll explain podcasts later.
Statistics
I’ve mentioned to a few people that I’ve read more than 200 books in 2020. It is not as impressive as it sounds. I’ve listened to a lot of audio books. I[…]
I recently started dabbling with Playwright Sharp having seen they now have (as the name suggests) some C# bindings for the automation library.
In order to try and put it through its paces a bit and decide if it is worth pursuing as a replacement or in addition to our Selenium based tests, I picked out one two more gnarly tests in the suite to do a comparison against. Please note this isn’t some pound for pound comparison of why you should use one tool over another, make your own mind up there
I’m not looking to shift existing automation prior to Selenium 4 being released as that will have a bunch of cool new stuff to explore too.
However, Playwright Sharp makes a strong case for itself in this space.
What I like about replicating in my hacking about time is that it’s given me a kick to do other things around my framework… like updating to .Net 5 for a start, refactoring bits and pieces and of course looking at Playwright Sharp itself.
First off, it is fast. I like fast, so fast it halved the execution time of the test I was looking at (This particular test I refer to does a bunch of API operations as well as iops on disk, in prep for the final outcome which you see in the browser) and the asynchronistic way that Playwright works can make waiting for DOM elements a lot less fiddly.
Actions, like clicks, auto-wait for UI[…]
The (best) five blogs we can read today. Check them out. How to write test cases for both manual and automated tests Written by: Gerie Owen Flaky Testing Written by: Michael Bolton Stop Softening Tough Feedback Written by: Dane Jensen on Peggy Baumgartner How to Fuel Tomorrow’s Energy Tonight Written by: Dan Rockwell How to Fix the Most Soul-Crushing Meetings Written by: Ron Carucci Quote of the day: “Teaching is learning things twice” -Joseph Joubert You can follow this page on Twitter
4.03.2021 | 12:05 קרא עוד...
Latest ISTQB Dumps available for Foundation Level Exam
Our team has prepared a comprehensive list of question papers for ISTQB Foundation Level (CTFL) Exam. These will be helpful for your exam preparation. Our carefully selected ISTQB Dumps are available online free of cost for download. Get the ISTQB Foundation Level dumps in one single location.
ISTQB Dumps Online
We are giving away free ISTQB Dumps online. The dumps are in pdf format and can be printed and easily used by any ISTQB aspirants. Get Free ISTQB Dumps from actual exams from Indian Testing Board, UKTB/BCS, ASTQB and other national boards. Over 1200 ISTQB Sample Questions and Answers available at one place. Download free ISTQB Certification Dumps 2021 now. ISTQB Foundation Level Exam Dumps based on new 2018 syllabus. PDF Study materials, guides for ISTQB exam. Download links given below.
Download ISTQB Dumps PDF
Click on the links below to download the practice papers.
ISTQB Foundation Level Sample Questions & Answers – 1
ISTQB Foundation Level Sample Questions & Answers – 2
ISTQB Foundation Level Sample Questions & Answers – 3
ISTQB Foundation Level Sample Questions & Answers – 4
ISTQB Foundation Level Sample Questions & Answers – 5
ISTQB Foundation Level Sample Questions & Answers – 6
ISTQB Foundation Level Sample Questions & Answers – 7
ISTQB Foundation Level Sample Questions & Answers – 8
ISTQB Foundation Level Sample Questions & Answers – 9
ISTQB Foundation Level Sample Questions & Answers – 10
ISTQB Foundation Level Sample Questions & Answers –[…]
Yesterday, I attended Unit Testing for Grown ups, a webinar with Gil Zilberfeld. Despite the title, it wasn't a tech-heavy tour through testing strategies, test doubles, or testability but instead a series of business arguments in favour of testing, primarily at the unit level. If I had to sum it up in a couple of bullets, it'd be something like this:developers, your work does not start at the first line of production code and end when you pushmanagers, your teams can probably work smarterAnd if I had a few sentences, it'd go like this:The goal of a software development group is to solve problems by writing code that "works" and is maintainable. It is usually the case that as a codebase expands unintended side-effects occur more frequently and the costs of integration, testing, and bug fixing grow.How to reduce these costs? Test first, and mostly at the unit level.But the tests have to be good tests so developers should train their creative skills for thinking about possible problems, and then provide coverage for the right set of them. This will be easier if the code is testable. Which means that testability needs to be part of the design of the system. Test-Driven Development could be a great way to address all of the points above but it can be hard to get your head around the cost-benefit payoff (as a developer and manager), hard to begin, and then also hard to maintain the discipline.
The (best) five blogs we can read today. Check them out. Don’t Lose Track of This Written by: Steve Keating You’re Not Paid Based on Your Performance Written by: Jake Rosenfeld How Emotion Regulation Influences Social Anxiety Written by: Courtney Beard Ph.D. Managing The Workplace Experience: How To Get It Right Written by: Meghan M. Biro Creating the Space for People to Learn Together Written by: Elisabeth (Lisi) Hocke Quote of the day: “Great things happen to those who don’t stop believing, trying, learning, and being grateful.” -Roy T. Bennett You can follow this page on Twitter
2.03.2021 | 11:26 קרא עוד...
Most modern online payment services offer easy-to-use, fast and secure ways to pay Here’s a list of some of the most popular online payment services:Digital Wallet ( E wallet)A digital wallet refers to software, an electronic device, or an online service that enables individuals or businesses to make transactions electronically. It stores the payment information of users for different payment modes on various websites. PayPalPayPal is one of the most dominant payment methods available today. over 20 million UK shoppers use PayPal each year in the UK and 7 million businesses worldwide use their platform to accept payments. PayPal is an eCommerce payment processing company that allows users to set up a PayPal account and pay a fee for each cash transaction. Many customers prefer to checkout with PayPal because it’s so simple and quick to use.Amazon PayAmazon Pay is another big name in the online payment space. Similar to PayPal, Amazon Pay is a digital payment processing service that allows customers to pay online using their Amazon payment methods on third party websites.Amazon Pay uses the details already stored on the shopper’s Amazon account to complete the transaction and provide a speedy checkout experience.eBay Managed PaymentseBay’s managed payment program allows the marketplace to process the payments directly by enabling customers to enter payment information and process payments without having to travel to a third-party site and leave the eBay interface. customers can benefit from a payment experience all through a single site, which includes multiple[…]
Lisa the IT Support Dog
The Importance of Exploratory Testing
My first encounter with exploratory testing (ET) was in 2009, when I worked as a test consultant for a Swiss company. Someone had the wonderful idea of updating the system, which was stable and well tested, from plain .NET to Silverlight and migrating the database from something-or-other-that-was-thought-to-be-outdated to Oracle. At the same time.
A few years earlier I’d had the pleasure of working with a great Finnish guy who held very strong opinions about the stupidity of making two major changes to a system at the same time. Opinions with which I fully agreed.
One Friday afternoon I was sat with a fellow tester, a cool German chap, when the first delivery of the revamped system was made. The test manager on the project told us to do some ET, by which he meant ad‑hoc testing. Both of us testers had plenty of testing experience and had been on the project for over a year, and we set about our task with gusto. Within an hour we’d found about forty issues between us. The programmers, a very capable bunch, made some changes to the code to allow us to trace the problems more easily. Once again, we testers set about the task with enthusiasm – I do like finding bugs – and found another forty-or-so problems. That spelt the end of ET on the project.[1]
Several years have passed since then, and the idea of what ET is, and what[…]
This post is, belatedly, inspired by the Ministry of Testing blog idea: The Struggle with Learning to Code. I have a Computer Science degree, and have been programming for a while. (I started doing it as a hobby, and then studied it, and then got paid to do it.) I struggle with learning to code, and have for a while.
Really?
Given my background, why do I struggle? The simple answer is that there’s so much to learn. What’s worse, my To Learn list gets bigger over time – new things are added to it more quickly than I can learn things off it.
Learning to code is like walking up the down escalator
Big divisions
I started coding in BASIC, and then Z80 machine code. After I graduated, my first job was writing C. As a result, I was comfortable with procedural programming. Switching to Object Oriented was a struggle, and took quite a while. I had been taught OO at university, but it wasn’t in my mental muscle memory and instead took conscious thought over quite a while. Signs of someone still making this transition from procedural to OO are things like God classes, very long methods, anaemic models and so on.
Another big division is functional programming, because it changes how you think about encapsulation, state, loops, breaking work down (things like currying functions) and so on.
Recently I’ve dabbled in quantum computing, which is different again. Code becomes probabilistic rather than deterministic. The world is divided[…]
This month I've been taking the Bug Advocacy course at the Association for Software Testing. It's been ten years since I took the introductory Foundations course, the first in the Black Box Software Testing series, and with this degree of hindsight I can see how fundamental that was in how I like to test. I've done plenty of learning in the decade since I started testing, so much of the material in Bug Advocacy is not new to me. That doesn't detract from the value of the course. I've taken the opportunity to refresh my memory, and to look at how the other students interpret the same material and how they go about the practical exercises, and compare that to my own approach. I love that these courses are run with small cohorts, emphasise practice to reinforce theory but also to ask questions of it, and require that students review each other's work as an aid to learning. Each week there are exercises that have the students interact with each other and software. We then write reports and reviews which themselves are reviewed and reported on. If that sounds convoluted, or even meta, don't be fooled: on a bug reporting course in particular, the concentration on data gathering, organisation, and dissemination is incredibly rewarding. Tester credibility and influence is a key element in the course, emphasised repeatedly. If we, and the information we provide, and the actions we take, have the respect of those we work with then we are[…]
Looking around test-related forums, social media accounts, and blogs like this one, you might notice more testers talking about testing APIs. It's with good reason. As I've mentioned plenty of times in previous articles, API testing is an essential part of modern software development and QA. As more applications rely on these interfaces, it's up to us as testers to ensure they work well across the board.Here on Dev Tester, I've written a few articles covering API testing, such as how to create fast and reliable automated test suites with some JavaScript libraries and things to consider when validating your APIs. This article adds another layer of testing to the mix for making sure your API can withstand expected and potential workloads - load testing.You might think that load testing is a complex skill to learn and put into practice. Fortunately, load testing isn't a difficult skill to add to your toolbelt. You have a wide selection of load testing tools, both commercial and open-source, so you'll likely find a tool that's simple yet powerful enough to fit your needs.One such tool I recently discovered is called Artillery. I took the toolkit for a spin on a small project and was impressed with how easy it lets you create load-testing scripts compared to other tools I've used in the past. Read on to learn how simple it is to get Artillery up and running in a real-world project and make sure your APIs are battle-tested.Why is load testing an API[…]
The (best) five blogs we can read today. Check them out. Think Again: The Power of Knowing What You Don’t Know Written by: Michael McKinney First Two Steps to Creating Resilience Written by: Leo Babauta Free Resources to Get Your Testing Practice On Written by: Dennis Martinez Zero Bug Tolerance Written by: Karl-Sander Erss 7 Ways to Give Support Without Prolonging Incompetence Written by: Dan Rockwell Quote of the day: “You must include the sad parts, because they are part of the story, and they have to be part of the dreams.” -Lois Lowry You can follow this page on Twitter
2.03.2021 | 12:00 קרא עוד...
Jumping in to a Protractor timeout problem
What to do when Protractor tests start failing, and Angular becomes unstable.
Hey!
This is my second bloggers club post, and again, I’m just scraping through on time nope I’m late.
The topic this time is:
Your struggles/successes with automation
I’m going to tell you what I’ve learned recently about Protractor and Angular stability.
Firstly, I’ll introduce Protractor, and how it works. Then I’ll tell you about a problem we had, and how we solved it.
Let’s begin!
Angular and Protractor
The frontend of our web app is written in Angular. For E2E testing, we use Protractor.
Protractor is a testing framework specifically designed to work with Angular. It’s really cool. Protractor can be used on non-Angular apps too, but partnering it with Angular is where its power lies.
The Testability class and “waitForAngular”
Every Angular app has a Testability class. The Testability class provides some information about the apps ‘readiness’ for testing.
Basically, the app knows when it is ‘stable’ - when it has loaded all elements to the page, finished processing, that sort of thing.
Using these functions, Protractor can be aware of when an Angular app is ready to be tested. Behind the scenes, it has a boolean property called waitForAngular, that defaults to true.
Because Protractor waits for Angular to be stable before running, you don’t have to explicitly wait for elements to appear, or play about with timeout settings for slow loading pages.
You can turn this feature[…]
The fact that Cypress is running inside the same context as the tested application is one of its greatest advantages. I wrote about this in previous posts about Page Objects vs. App Actions and also in article about opening a new tab in Cypress. This architecture allows us to look into the functions our app is executing. It also allows adjust the app’s context such as browser preferences and time. The latter is the subject of this blog. Let’s look at a simple app I’ve made for this article. It basically just opens up and starts counting seconds. Like a stopwatch, but resetting only on refresh. The way this app works, is that inside this app, we have a setInterval() function. This is a JS function that takes two arguments. First one is the function we want to run, and the second one is time in milliseconds, that tells our function how often should it run this function. setInterval(updateTime, 1000); Our updateTime() function does all the work in this app. The way it works is pretty simple. There are two Date objects in our app. One will get our time at the moment we open our app, and the other one is created every time our updateTime() function is called. These two are then compared so every second we get a new time information. We then take the `` element, and update it’s text with the new time. The .clock() function in Cypress allows us to tap into all the[…]
1.03.2021 | 3:37 קרא עוד...
This month EuroSTAR organises their very first deep dive week on Agile. From 22nd – 26th March we will be exploring many facets of Agile including QA, Quality and more. For the first time we will be hosting two AMAs (Ask Me Anythings) with two experts in Agile, Bob Galen and Lisa Crispin. See the full details below. Additionally we have some great webinars to catch up on. I’ll be closing the week with my Friday session on built-in quality.
You can register to any of the sessions at the conference site: Register for the agile deep dive week
By this part of the series, we have covered how to open the job market up to a wider talent pool and have looked into how to make Job Specs inclusive, the next step is to look at how we can make the interview process more accessible for all candidates, not just those classed as neurodivergent.
For someone with a neurodiverse condition, the idea of having to communicate and sell themselves to strangers could be akin to torture, this is partly why a lot of neurodiverse candidates will avoid disclosing their condition. They will feel like it will be held against them, rather than being supported and allow for the interview to be adapted for them.
Interviews don’t give a true reflection of whether someone could do a job anyway, but for a neurodiverse candidate, they may be more than capable of doing the job well, but will not get a chance to prove that because they hadn’t found a way to talk about it in the way the interviewees want them to talk about it. Something doesn’t add up here, but the interview process is probably here to stay for a long time yet.
What Can We Do to Make It Less Torturous?
Everything should be done to make all candidates feel as relaxed and informed of the process as possible. without this, any Neurodiverse candidate will instantly feel completely overwhelmed with the lack of knowing what to expect. This alone could cause someone with Autism to become very[…]