Which automation tool | framework should I choose for my new project?

izzy's playlists!

Origami Around

⁂

祝日 / Permanent Vacation
we're not kids anymore.
trying on a metaphor
Sweet Seals For You, Always
RMH
Alisa U Zemlji Chuda
I'd rather be in outer space 🛸
macklin celebrini has autism

ellievsbear

★

roma★
noise dept.
Mike Driver
KIROKAZE
d e v o n

Kaledo Art
almost home
seen from Australia
seen from Iraq
seen from United Kingdom
seen from Jordan

seen from Brazil

seen from United States

seen from Malaysia

seen from Türkiye
seen from Indonesia

seen from Singapore

seen from United States

seen from China
seen from Brazil

seen from Singapore

seen from Brazil
seen from Indonesia

seen from Australia
seen from Singapore
seen from United States
seen from United States
@software-qa-automation
Which automation tool | framework should I choose for my new project?
Everything I know about software development, testing, Python as tutorials.
Share your videos with friends, family, and the world
Courses on Python, Pytest, Docker, Locust etc.
My first job in technology was a QA internship. The summer between my freshman and sophomore years, I tested the first release of Paradox for Windows at Borland. As an intern, I started by following someone else’s QA test plan – dutifully checking each test off the list. After a few weeks, I knew m
Perhaps a more likely reason that exploratory testing is called unstructured is that outsiders may not perceive any commitment to a particular structure. But that’s really about trust, competence, and culture, all of which are manageable without forcing testers to stop using their minds and exercising their technical discretion. After all, we don’t ordinarily demand that a taxi driver show us his “plan” for driving, because our culture encourages us to trust in the intentions and competence of taxi drivers. When this trust is not present, as I have experienced in a couple of countries, then I actually will discuss the structures of an upcoming taxi ride before I get into the car.
https://www.satisfice.com/exploratory-testing
Testing is not A science; testing IS science. Imagine a science teacher in grammar school who does a chemistry demonstration. First, the teacher describes the setup and the equipment. Then he explains the chemicals and describes the reaction that will occur. He mixes two transparent liquids together, and you see the resulting solution slowly turns dark blue. This is commonly called a “science experiment,” but only by non-scientists. The teacher knew exactly what would happen; therefore, it is more properly called a demonstration. But there is a major difference between a physicist and a software tester— the things we testers experiment upon are far less known and far less stable. No physicist worries about needing to “regression test” physical laws because they might have been changed the previous night. Yet, that sort of thing does happen to testers, so our learning curve never flattens out, and our test designs must be allowed to change.
https://www.satisfice.com/exploratory-testing
Regular Expressions (Regex) Tutorial: How to Match Any Pattern of Text
The Internet: How Search Works
The Internet: Encryption & Public Keys
The Internet: HTTP & HTML
The Internet: Packets, Routing & Reliability
The Internet: IP Addresses & DNS