he icon   en icon

LOGIN
התחברות או הרשמה
Avatar
להמשך הרשמה ידנית – לחץ על כפתור ההרשמה, להרשמה/כניסה מהירה בעזרת חשבון רשת חברתית – לחץ על הלוגו בכותרת

אפס סיסמה - שכחתי את שם המשתמש

שם משתמש
סיסמה
זכור אותי

RSS מהעולם

  • Fragile Tests vs Flaky Tests

    Some call them flaky tests. Some call them fragile tests. Or unstable. I say it’s neither, it’s the code. Nobody likes them, regardless. But here’s something interesting I heard in a conversation with one of my clients. He said: “I like calling them flaky tests, not fragile”. Why? I asked. They mean exactly the same thing. Ah, that’s true, said the developer. But it sounds different. “Fragile tests” sounds like being fragile is the intrinsic property of the tests. They are just like that, there’s nothing we can do about it, and we’ll just have to live with them like that. “Flaky tests” sounds a little different. It sounds like someone (not pointing fingers here, but you know who you are) hasn’t done enough to remove the flakiness. It is not a part of the test, it is something that clung to it, like what you’re thinking about right now. And it can (and should) be removed. In other words, “fragile tests” don’t sound like they carry responsibility, while “flaky tests” do. I liked this explanation. The responsibility for stability and consistency is there regardless of how we call it (whether it is in the code, test, or both). It’s just in one case, if you listen closely, you’ll hear the test whispering to you: “Don’t leave me like that. Fix us”. And it is our responsibility. For more a-fixing tests, and testability improvement, check out my “API Testing for developers” workshop. Because we are responsible developers, yes we are.[…]

    20.02.2024 | 1:56 קרא עוד...
  • Get insights from “The World of W. Edwards Deming” by Cecelia S. Kilian

    Get insights from “The World of W. Edwards Deming” by Cecelia S. Kilian Cecelia S. Kilian was W. Edwards Deming‘s long-term secretary. She created this book which contains her memories, and many curated documents from Deming. I read this book with the Profound Deming Book Club and it made me think about why I am interested in Deming. The details of Deming’s life are interesting, however I am interested in him because I want the same things he did. I want companies to be successful businesses by continually improving the quality of their products and services.  The most interesting chapters in the book are Deming’s notes on what he taught Japanese management in 1950 at lectures which he was invited to give by the Japanese Union of Science and Engineering. The book includes notes on his lecture at Mt. Hakone. If I understand the history of the idea I understand the idea more deeply. I found it fascinating to read in the notes of lectures from nearly 75 years ago many ideas that are used today. These points are taken from the chapters about Deming’s 1950 lectures : Building quality into a product: “You can not inspect quality into a product”. ”You must build in quality” [1] The use of control charts to analyse processes, as is done in many industries today. [1] User testing, which he describes as consumer research.” Consumer research is communication between the manufacturer and users and potential users” of the product or service”. [3] The plan-do-study-act cycle. Today the plan-do-study-act cycle describes a software development team’s iterations[4] and[…]

    20.02.2024 | 1:37 קרא עוד...
  • Beyond the Hype: Can technology sustainability really make a difference?

    In this episode, Oliver Cronk is joined by experts including Jeremy Axe, Group CTO at DS Smith, and consultants Darren Smith and Katie Davis from Scott Logic. Together, they unpack topics like the energy usage and carbon emissions of IT infrastructure, the challenges in accurately measuring sustainability, and whether claims of ‘green tech’ are substantiated or just hype. The conversation covers the nuances around operational versus embodied carbon emissions, the sustainability trade-offs involved in cloud versus on-premises hosting, and the need for transparency and standards around eco-friendly tech claims. Links from the podcast Proposed Technology Carbon Standard – open sourced by Scott Logic under a CC BY-NC-SA 4.0 licence Scott Logic blog posts on Sustainability – including the Conscientious Computing series DS Smith’s approach to sustainability Scott Logic’s approach to supporting technology sustainability Subscribe to the podcast Apple Podcasts Google Podcasts Spotify

    19.02.2024 | 9:42 קרא עוד...
  • AI Powered Test Management

    Test management isn’t an easy task. It requires lots of skills from planning, to executing testing and to help others do their job right. There are plenty of test management tools on the market. Many of them offer lots of features, but still test management requires lots of manual steps. With the latest product update from Tricentis Test Management for JIRA, this might change. The Tricentis team added some AI features to TTM for better test case and bug ticket creation. One year ago, I already presented TTM on my channel, and I am now more than happy to give you the latest product tour. Enjoy the video. Please check the video description for more links for you to follow up. Leave a like and comment at the video to support me. Don’t forget to subscribe to my channel to not miss any new videos. #HappyTesting The post AI Powered Test Management appeared first on Adventures in QA.

    19.02.2024 | 2:38 קרא עוד...
  • Sharpening the Axe

    Sharpening the Axe In the heart of a dense, unyielding forest, a lumberjack stands, axe in hand, ready to tackle the colossal task before him. The trees, towering and formidable, are not unlike the complex software systems testers face in the digital realm.This lumberjack, however, knows something crucial that sets him apart — the value of sharpening his axe. This tale is not just one of wood and steel but a powerful metaphor for the essence of software testing in today’s rapidly evolving tech landscape.The Essence of PreparationJust as a lumberjack spends time sharpening his axe to ensure clean, efficient cuts, a software tester must continuously hone their skills to navigate the intricate world of software development. This process is not just about refining technical abilities; it’s about deepening understanding, expanding knowledge, and embracing new methods to ensure that when the time comes to test, the process is as effective and efficient as possible.At the core of effective testing lies a profound understanding of the product itself. Like the lumberjack who studies the grain, species, and nuances of the trees, testers must immerse themselves in the product they are testing. This means going beyond the surface level to understand the business logic, the technology stack, and the user experience. It’s about seeing the forest for the trees, understanding how each component interacts with another, and anticipating how changes in one area can ripple through the system.Knowing the Domain and UsersEqually important is the tester’s knowledge of the domain and the users. The lumberjack must understand the forest’s ecosystem,[…]

    19.02.2024 | 1:21 קרא עוד...
  • A “Full Stack Developer” Blames ‘Chrome Releases’ for Unreliable E2E Test Execution, Absurd!

    A “Full Stack Developer” Blames ‘Chrome Releases’ for Unreliable E2E Test Execution, Absurd! A typical fake automated tester blames everything but his/her capability.Continue reading on Medium »

    18.02.2024 | 12:58 קרא עוד...
  • Automated GraphQL Testing: Ensuring Stability and Reliability

    In the ever-evolving landscape of web development, GraphQL has emerged as a powerful query language and runtime for APIs. With its flexibility and efficiency, GraphQL introduces...

    18.02.2024 | 10:29 קרא עוד...
  • Vanilla Flavour Testing

    Vanilla Flavour Testing I have been pairing with a new developer colleague recently. In our last session he asked me "is this normal testing?" saying that he'd never seen anything like it anywhere else that he'd worked. We finished the task we were on and then chatted about his question for a few minutes. This is a short summary of what I said.I would describe myself as context-driven. I don't take the same approach to testing every time, except in a meta way. I try to understand the important questions, who they are important to, and what the constraints on the work are. With that knowledge I look for productive, pragmatic, ways to explore whatever we're looking at to uncover valuable information or find a way to move on.I write test notes as I work in a format that I have found to be useful to me, colleagues, and stakeholders. For me, the notes should clearly state the mission and give a tl;dr summary of the findings and I like them to be public while I'm working not just when I'm done. I use notes to keep track of test ideas, hypotheses, findings, coverage, evidence, and so on. I am pleased when someone notices something I've missed or a mistake I've made because it means I have the opportunity to learn and correct. Because I am context-driven, I also sometimes don't write test notes in this way.I have worked hard to reduce the friction in my work by finding practices that keep me[…]

    18.02.2024 | 12:22 קרא עוד...
  • Why should we test in the design phase? How should we go about it?

    Recently I reflected on how to explain to someone else about why software testers need to be involved in the design phase and secondly, if they are involved in the design phase, how should they go about it? I’ve done some googling and learned from others, but I haven’t found quite what I’m looking for.I’ve written a lot of things on my blog about getting involved early and also, taken note of lots of things in the testing community around testing requirements. What about testing in the design phase? I have seen that yes, we should be included there and test the ideas, but why?The easiest way I can explain is that rubbish can be dumped into a river at any point. If you are just sitting at a hut watching the river flow past looking for rubbish, then you see it at one point, where you are sitting. Not actually where the problem got thrown into the river. See Previous blog post on sitting in a hut and assessing the river. So you should test in the design phase to see if any problems are getting chucked in at that stage.In the design phase what we are doing is testing the concept. The shape that an idea is forming into.Here are some questions I have formulated.How easy can we implement the design? Thinking about speed and costing. You should ask this question as sometimes they create a design that does not consider how long (speed) or how much (cost). There might be a[…]

    17.02.2024 | 2:19 קרא עוד...
  • Five for Friday – February 16, 2024

    Wow. This week went quickly – but the internet never fails to provide interesting things for me. Elisabeth Hendrickson wrote two fantastic articles this week. The first covers something I stress a lot – interview the company who is hiring you. The second builds on the first, and discusses manager failure modes. Read them both. I had to look if I posted this already. Either it’s a duplicate, or I can’t read, but either way, it’s worth reading (again). Yes, good DevEx increases productivity. Here is the data. Loved this post from Bryan Finster on being Too Smart to Make Mistakes I’ve contributed to a few tech career ladders in my life. Trish Khoo has a great write up of some of the behind the scenes that goes into creating a good career ladder. I knew some of this, but definitely not all. This was a nice article on The History of Port Numbers Hope you found something interesting – see ya’ in a week.

    16.02.2024 | 3:49 קרא עוד...
  • Glints in Leadership

    Glints in Leadership I talk quite a bit about leadership as creating spaces where people can thrive and grow. It suits my leadership style to lead in such a way. I get to amplify my strengths and work in a way that rewards me. It's a beautiful experience to see people back their ideas and abilities and venture into something new. Creating spaces is about allowing people the agency to decide how the work they're accountable for is executed. It's signalling that around here, your ideas and goals are valuable and will be listened to. It's the opportunity for you, if you wish, to determine what success looks like and then give you the tools to make that happen. That means being available to people, listening to them and allowing them to succeed on their terms. It takes time for those ripples of change to have an impact. They won't come out of obvious places. And often, they're only recognisable as a glint on water. But when you see it, do everything you can to nurture it and give it room to grow. You must protect it from the elements, and when it thrives, you must celebrate it. Not everyone is going to agree with this approach. Some may see this as a threat or dismiss it as passive leadership. I've come to realise that this space is for them, too. As a leader, you offer this space to everyone, even those who operate and behave differently from you. You don't have to[…]

    16.02.2024 | 3:24 קרא עוד...
  • Try the Awarding-Winning BuildWise Live on the TestWisely Platform

    Try the Awarding-Winning BuildWise Live on the TestWisely Platform Try the award-winning Continuous Testing Solution on the Cloud.Continue reading on Medium »

    16.02.2024 | 1:35 קרא עוד...
  • 5 Key Reasons to Choose Private Cloud for Mobile App Testing

    Test Guild - Automation Testing Tools Community 5 Key Reasons to Choose Private Cloud for Mobile App Testing Remote work has fixed a lot, but it's made testing mobile apps a real pain for QA teams. How do we make sure that developers and testers can use the latest devices? Like iPhones, Androids, and even niche gear like AR headsets from home? Shipping devices across the world is impractical. And public Cloud device […] You’re reading 5 Key Reasons to Choose Private Cloud for Mobile App Testing, originally posted on Test Guild - Automation Testing Tools Community - and copyrighted by Joe Colantonio

    16.02.2024 | 12:54 קרא עוד...
  • Hello, World! The best of Esoteric Languages

    Esoteric languages are mind boggling and a lot of fun, even just writing Hello World! Come check out my 5 favourites. The post Hello, World! The best of Esoteric Languages first appeared on The Quality Duck.

    16.02.2024 | 11:38 קרא עוד...
  • Sharing is caring - Intro to Jenkins shared libraries

    Sharing is caring - Intro to Jenkins shared libraries  Whether you're just dipping your toes into the world of automation infrastructure, or already crafting your first jobs to automate your test execution, Jenkins is your new best friend. In this blog post, we will talk a bit more about the practice of infrastructure as code, its relevance to test automation, and how you can avoid code duplications, align with industry best practices, and enable velocity, maintainability, and collaboration.So, whether you're a seasoned pro or just starting out, let's dive into the world of Jenkins Shared Libraries and see how they can make your life easier.Jenkins Shared Libraries play a crucial role in the realm of Infrastructure as Code (IaC). So, what are they exactly? Think of Jenkins Shared Libraries as your secret stash of code snippets, neatly organized and ready to be plugged into your pipelines whenever needed.Let's explore the aspect of reusability within Jenkins Shared Libraries:Reusability is the cornerstone of efficiency in software development, and Jenkins Shared Libraries excel in promoting this principle.Imagine you've crafted a pipeline for executing your test automation suite, complete with parameterized options for test suite type, target device/platform, environment, and concurrency. You've also developed a versatile runner method capable of translating user parameters into actionable commands for initiating test runs.Now, consider the scenario where you want to set up a nightly execution or integrate additional functionalities into your pipeline. Rather than starting from scratch or duplicating code, you can encapsulate the existing functionality, including the runner method and parameter handling logic, into reusable components within[…]

    16.02.2024 | 2:47 קרא עוד...
  • What Is in Your Organizational Closet?

    What Is in Your Organizational Closet? Do you need to clean out your organizational closets? Closets are where we store useful things. But they also tend to accumulate items that no longer provide value.I’m having new flooring put in on the second floor of my house, which requires that I empty all seven closets. It’s been quite a task, full of mysteries and memories.  I made many trips to the local thrift shop with donations. There were a few wonderful finds, too. But mostly, I rediscovered things that had been useful at one time, but no longer provided value. I’d been holding onto them because they were out of sight and out of mind. Or because they’d been important at one time, and might be useful again (haha). Your organization may have physical closets that could use a bit of a clean out….but your metaphorical closets probably need attention, too. Over time, organizations accumulate policies, habits, and beliefs. Once put in place, they often don’t get much thought. They’re just there, part of the background, still influencing current actions. Maybe still useful, maybe not. Some examples: Attendance policies that don’t reflect the realities of remote and hybrid work, or workers’ desire for flexibility.  Beliefs about motivation that rely on extrinsic rewards–or punishment. Job descriptions that emphasize individual work, and don’t account for highly collaborative, interdependent work.  Such things take up time and mental space. They shape patterns of behavior. They can create confusion and cynicism, especially when policies or beliefs are in conflict with each other[…]

    15.02.2024 | 5:03 קרא עוד...
  • From First Selenium Test at 12 to Published Author: My Daughter’s Ten-Year Journey in E2E Test Aut

    From First Selenium Test at 12 to Published Author: My Daughter’s Ten-Year Journey in E2E Test Aut The importance of choosing the right tech stack to learn, which was raw Selenium WebDriver + RSpec, with TestWise IDE.Continue reading on Medium »

    14.02.2024 | 12:52 קרא עוד...
  • Making Releases Routine

    Making Releases Routine Last year I experienced something I had not experienced for a while: a four month stabilisation period. A core of the work of testing-related transformations I had been doing with three different organizations was to bring down release timeframes, from these months long versions to less than an hour. Needless to say, I considered the four month stabilisation period a personal fail. Just so that you don't think that you need to explain me that failing is ok, I am quite comfortable with failing. I like to think back to a phrase popularised by Bezos 'working on bigger failures right now' - a reminder that too safe means you won't find space to innovate. Failing is an opportunity for learning, and inevitable when experimenting in proportion to successes. In a retrospecting session with the team, we inspected our ways and concluded that taking many steps away from a good known baseline with insufficient untimely testing, this is what you would get. This would best be fixed by making releases routine. There is a fairly simple recipe to that:Start from a known good baselineMake changes that allow for the change you want for your usersTest the changes in a timely fashionRelease a new known good baselineThe simple recipe is far from easy. Change is not easy to understand. And it is particularly difficult if you only see the change in small scale (code line) and not in system (dependencies). And it is particularly difficult if you only see the system but not the small[…]

    14.02.2024 | 12:28 קרא עוד...
  • How to build a QA Mindset from scratch - Chapter 4 - Automation Testing

    How to build a QA Mindset from scratch - Chapter 4 - Automation Testing Over the past few months, I've come across several intriguing articles discussing automation, with one particularly emphasized statement: "Automation is an absolute necessity; everything must be automated." However, this assertion is fundamentally flawed. Not all processes should be automated, prompting us to question the rationale behind automation in the first place.The initial step involves elaborating on a checklist, and only if the majority of criteria are affirmative, should you proceed to the next stage:Are you familiar with the products/services you work with?Do you plan to implement or anticipate the use of unit or component tests to validate configurations at an early stage?Have you documented manual regression tests?How frequently do you release to production? If not, have you established robust regression tests to validate core features that must remain functional despite code changes?Do you require additional time for exploratory testing?If you answer yes to three of these questions, it indicates readiness to begin considering and implementing an automation roadmap plan for your team.When incorporating automation tests into the test strategy, the main consideration should be the stability of the product. This entails assessing the frequency of changes to core features in production. Additionally, it's crucial to evaluate the robustness and stability of the existing regression suite. Once these factors are established, a plan can be devised to automate using the regression suite as a foundation.If it's the inaugural venture within the organization, initiating a Proof of Concept (POC) is imperative.How?This required allocating dedicated time, which should be mutually agreed upon with[…]

    14.02.2024 | 11:41 קרא עוד...
  • Leveraging Excel for Streamlined API E2E Testing with Python Behave

    Leveraging Excel for Streamlined API E2E Testing with Python Behave Excel and Python Behave: A Powerful Combination for Simplified API TestingContinue reading on Testopia »

    14.02.2024 | 7:17 קרא עוד...
 

חדשות מעולם הבדיקות

  • Fragile Tests vs Flaky Tests

    Some call them flaky tests. Some call them fragile tests. Or unstable. I say it’s neither, it’s the code. Nobody likes them, regardless. But here’s something interesting I heard in a conversation with one of my clients. He said: “I like calling them flaky tests, not fragile”. Why? I asked. They mean exactly the same thing. Ah, that’s true, said the developer. But it sounds different. “Fragile tests” sounds like being fragile is the intrinsic property of the tests. They are just like that, there’s nothing we can do about it, and we’ll just have to live with them like that. “Flaky tests” sounds a little different. It sounds like someone (not pointing fingers here, but you know who you are) hasn’t done enough to remove the flakiness. It is not a part of the test, it is something that clung to it, like what you’re thinking about right now. And it can (and should) be removed. In other words, “fragile tests” don’t sound like they carry responsibility, while “flaky tests” do. I liked this explanation. The responsibility for stability and consistency is there regardless of how we call it (whether it is in the code, test, or both). It’s just in one case, if you listen closely, you’ll hear the test whispering to you: “Don’t leave me like that. Fix us”. And it is our responsibility. For more a-fixing tests, and testability improvement, check out my “API Testing for developers” workshop. Because we are responsible developers, yes we are.[…]

    20.02.2024 | 1:56 קרא עוד...
  • Get insights from “The World of W. Edwards Deming” by Cecelia S. Kilian

    Get insights from “The World of W. Edwards Deming” by Cecelia S. Kilian Cecelia S. Kilian was W. Edwards Deming‘s long-term secretary. She created this book which contains her memories, and many curated documents from Deming. I read this book with the Profound Deming Book Club and it made me think about why I am interested in Deming. The details of Deming’s life are interesting, however I am interested in him because I want the same things he did. I want companies to be successful businesses by continually improving the quality of their products and services.  The most interesting chapters in the book are Deming’s notes on what he taught Japanese management in 1950 at lectures which he was invited to give by the Japanese Union of Science and Engineering. The book includes notes on his lecture at Mt. Hakone. If I understand the history of the idea I understand the idea more deeply. I found it fascinating to read in the notes of lectures from nearly 75 years ago many ideas that are used today. These points are taken from the chapters about Deming’s 1950 lectures : Building quality into a product: “You can not inspect quality into a product”. ”You must build in quality” [1] The use of control charts to analyse processes, as is done in many industries today. [1] User testing, which he describes as consumer research.” Consumer research is communication between the manufacturer and users and potential users” of the product or service”. [3] The plan-do-study-act cycle. Today the plan-do-study-act cycle describes a software development team’s iterations[4] and[…]

    20.02.2024 | 1:37 קרא עוד...
  • Beyond the Hype: Can technology sustainability really make a difference?

    In this episode, Oliver Cronk is joined by experts including Jeremy Axe, Group CTO at DS Smith, and consultants Darren Smith and Katie Davis from Scott Logic. Together, they unpack topics like the energy usage and carbon emissions of IT infrastructure, the challenges in accurately measuring sustainability, and whether claims of ‘green tech’ are substantiated or just hype. The conversation covers the nuances around operational versus embodied carbon emissions, the sustainability trade-offs involved in cloud versus on-premises hosting, and the need for transparency and standards around eco-friendly tech claims. Links from the podcast Proposed Technology Carbon Standard – open sourced by Scott Logic under a CC BY-NC-SA 4.0 licence Scott Logic blog posts on Sustainability – including the Conscientious Computing series DS Smith’s approach to sustainability Scott Logic’s approach to supporting technology sustainability Subscribe to the podcast Apple Podcasts Google Podcasts Spotify

    19.02.2024 | 9:42 קרא עוד...

טיפים

לרשימה המלאה >>