Обложка канала

QA_PRO | Тестирование

5341 @qa_pro

Информация по обеспечению качества (QA), контролю качества (QC) и тестированию ПО

  • QA_PRO | Тестирование

    Any interesting books to read?
  • QA_PRO | Тестирование

    Testing Web Accessibility by Adrián Bolonio

    We want our web app to be effective, efficient, and satisfying for the user, but a lot of times we don’t think about the user experience for people with disabilities, including people with age-related impairment. How can automated a11y tests and manual test help us make our interface better? When we develop a new web application, we often put a lot of work on the design, on making it beautiful and usable. In other words, we want our web app to be effective, efficient, and satisfying for the user. But a lot of times we don’t think about the user experience for people with disabilities, including people with age-related impairments. Web accessibility (a11y ) means that people with disabilities can perceive, understand, navigate, and interact with websites and tools, and that they can contribute equally without barriers.” (Source: W3C - Web Accessibility Initiative). Our role as frontend and web developers is to create clear interfaces to make people understand and care about data, independently of their disabilities or impairments, but what we, developers, often forget is to ensure that the code we write follows the Web Content Accessibility Guidelines (WCAG), and the only way to achieve that is testing, either manual or automated. Automated web a11y tests can free up our QA team from manual testing every part of our application, but, they can’t automatically make our site accessible. We should use automated a11y tests as one step of a larger testing process. https://jsconfbp.com/speakers/adrian-bolonio About Adrian Hi, my name is Adrián Bolonio. I'm a Google Developer Expert in Web Technologies currently working as an Accessibility Software Engineering at GitHub as part of a talented, diverse, and motivated team that will work on making GitHub and the Internet a better and more accessible place for everyone. When I’m not at the office I enjoy a good read, working my way through any delicious recipe, and indulging my love for travelling to new places.

    YouTube
  • QA_PRO | Тестирование

    Software quality is not related to test cases, automation and shift left something. It is about your (and your engineers) knowledge and skills. Read books/articles about software engineering - it will help you a lot. --- en.m.wikipedia.org/wiki/Co…ramming) An image shows modules coupling in real project. I guess, 65% of senior developers and 90% of QAs around the world don't even know what that is.
  • Реклама

  • QA_PRO | Тестирование

    Incompetent and opinionated people are the biggest problem in IT
  • QA_PRO | Тестирование

    fortune.com/2023/07…ning/amp Nice one! They would be scared if they were to calculate how much money they spend on code reviews and how much value it provides 😅
    Shopify has calculated a 30-minute pointless meeting costs them up to $1,600

    "Time is money. If you have to spend it, you think about it."

    Fortune
  • QA_PRO | Тестирование

    Automation doesn’t find bugs. People find bugs, and automation plays a role (sometimes a very powerful role) in finding bugs. Tools don’t do stuff on their own. Automated checks don’t design themselves. Programs don’t set out to analyse output, or to produce the kind of input that can trigger problems. People do that stuff. A medium is something in between something and something else. Tools are media between ourselves and a job we want to do. Media enable, extend, enhance, accelerate, or intensify our capabilities. That’s fine when we're good at what we do; automation enhances our superpowers, allowing skilled testers to identify bugs in exactly the ways Katja describes in the post linked below. (An early version of my post didn’t include the link. My post started as a repost with comments, but LinkedIn appears to have forgotten that.) The key in all this is the skilled tester, since automation also allows bad testing to be done faster and worse than ever. Tools intensify our sight and our focus; they just as easily intensify blindness. Ever tried someone else's eyeglasses, or worn sunglasses at night? Ever noticed how binoculars restrict your field of view, even as they magnify the thing you’re looking at? Tools can help us to find certain bugs faster and more powerfully than we ever could on our own. They can also help to direct attention to trivial things, distracting us from the more important ones. Tools can help save time and effort for other things. Tools also require development, preparation, maintenance, interpretation and vigilance that can cost more time than we might be saving. When we say "automation finds bugs" we give credit to the wrong thing—the tool, instead of the tester using the tool. That opens the door for the tool vendors to suggest that testers don’t need skill; and for inept managers to believe that testers can be replaced by tools, or that "we should set 100% automated testing as the goal". Katja here tells stories of success. That's fine. But it’s Katja and her colleagues who deserve the credit for finding the bugs, using tools appropriately and skilfully. Automation *can help* *us* find bugs. --- Michael Bolton, RST
  • QA_PRO | Тестирование

    Code Red: The Business Impact of Code Quality • Adam Tornhill • YOW! 2022

    This presentation was recorded at YOW! 2022. #GOTOcon #YOW https://yowcon.com Adam Tornhill - Founder & CTO at CodeScene Programmer, Psychologist, Lisp Hacker, Speaker & Author of Several Books Including "Your Code as a Crime Scene" @codescene-softwareengineer6553 RESOURCES https://arxiv.org/abs/2203.04374 https://codescene.com/hubfs/web_docs/Business-impact-of-low-code-quality.pdf Adam https://twitter.com/AdamTornhill https://github.com/adamtornhill https://linkedin.com/in/adam-tornhill-71759b48 http://www.adamtornhill.com ABSTRACT Code quality is an abstract concept that fails to get traction at the business level. Consequently, software companies keep trading code quality for new features. The resulting technical debt is estimated to waste up to 42% of developers' time, causing stress and uncertainty, as well as making our job less enjoyable than it should be. Without clear and quantifiable benefits, it's hard to build a business case for code quality. In this talk, Adam takes on the challenge by tuning the code analysis microscope towards a business outcome. We do that by combining novel code quality metrics with analyses of how the engineering organization works with the code. We then take those metrics a step further by connecting them to values like time-to-market, customer satisfaction, and road-map risks. This makes it possible to a) prioritize the parts of your system that benefit the most from improvements, b) communicate quality trade-offs in terms of actual costs, and c) identify high-risk parts of the application so that we can focus our efforts on the areas that need them the most. All recommendations are supported by data and brand new real-world research. This is a perspective on software development that will change how you view code. Promise. [...] TIMECODES 00:00 Intro 00:20 What is technical debt? 05:23 Visualize technical debt & code complexity 14:46 Quantify the business impact of code quality 19:02 Does code quality matter? 28:13 Prioritize remediation to large amounts of red code 30:04 Resources 40:25 Q&A Download slides and read the full abstract here: https://yowcon.com/sydney-2022/sessions/2277 RECOMMENDED BOOKS Adam Tornhill • Software Design X-Rays • https://amzn.to/3DEeEnI Adam Tornhill • Your Code as a Crime Scene • https://amzn.to/3FI5E2V Adam Tornhill • Lisp for the Web • https://leanpub.com/lispweb Adam Tornhill • Patterns in C • https://leanpub.com/patternsinc Caitlin Sadowski & Thomas Zimmermann • Rethinking Productivity in Software Engineering • https://amzn.to/41ztwjs https://twitter.com/GOTOcon https://www.linkedin.com/company/goto- https://www.facebook.com/GOTOConferences #CodeScene #CodeAsACrimeScene #AdamTornhill #TechnicalDebt #Legacy #LegacyCode #DeveloperProductivity #CodeComplexity #Complexity #CodeSmells #RedCode #GreenCode #CodeQuality Looking for a unique learning experience? Attend the next GOTO conference near you! Get your ticket at https://gotopia.tech Sign up for updates and specials at https://gotopia.tech/newsletter SUBSCRIBE TO OUR CHANNEL - new videos posted almost daily. https://www.youtube.com/user/GotoConferences/?sub_confirmation=1

    YouTube
  • QA_PRO | Тестирование

    False positive 🤣
  • QA_PRO | Тестирование

    🍿🍿
  • QA_PRO | Тестирование

    Coding Interviews Be Like

    like and subscribe coding interviews be like #beluga #rambda #codinginterview #coding #programming #skit #discord #discordmeme #memes #comedy

    YouTube
  • QA_PRO | Тестирование

    NFRs and QA (or QC) --- A way of measuring the maintainability of the software, part 1 --- Halstead Complexity, 1977 en.m.wikipedia.org/wiki/Ha…measures www.win.tue.nl/~asereb…1/10.pdf --- It also allows to predict the number of bugs in the software, and the accepted error ratio, which might be very useful for QA / QC activities and quality goals
  • QA_PRO | Тестирование

    Defect clustering in real life :)
  • QA_PRO | Тестирование

    What do I think about ISTQB certifications? - certificate itself --- Let's start with what we have for foundation level: - unlimited attempts (even daily, if you have enough money 😅) - 26/40 correct answers - ~250$ / online / "automatic check" - no information about failed questions (meaning you can't improve... or cheat?) - all certificates are the same, you don't see the score, only a Pass/Fail - valid forever --- In result, if you have 2 testers with this certificate: - one, having 37/40 correct answers from the first try without visiting "learning centers" - meaning he/she knows something - and the other one, having 26/40 from the 5th try with visiting(paying) for a course in the "learning center" - meaning he/she just got lucky enough you, as a an employer, are not able to select the better(first) candidate, because you just don't know the score and attempts, and they look identical to you, but they are definitely not 🤷‍♂️ --- Now, let's compare it to IELTS: - 1 attempt / 31 days - there is no pass/fail. You get scores which are visible to everyone - ~220$ / in person / manual check by a professionals - you get the information about failures, meaning you can improve - all certificates are different (because scores are different) - valid for 2 years As an employer - you see everything, can easily compare candidates and define which level of knowledge (aka B1/B2/C1) is needed for you --- Looks way better, right? Because IELTS certificate is a proof of knowledge (even if it is A2) --- So, to sum up: - from employer (and employee) point of view - the ISTQB certificate is almost useless, because it does not provide any data about candidate skills and does not prove knowledge - from ISTQB point of view - the second candidate is perfect (just calculate the $$$) - from price point of view - 250$ for an online test which is being generated and checked automatically, its kinda 🤯 --- #istqb
  • QA_PRO | Тестирование

    Is it only me who does not understand why QA Leads with ISTQB Test Manager certifications and 10+ years of experience are "creating test cases" and "test mobile applications"? 🙃 #istqb
  • QA_PRO | Тестирование

  • Реклама

  • QA_PRO | Тестирование

  • QA_PRO | Тестирование

    How ChatGPT actually works

    Since its release, the public has been playing with ChatGPT and seeing what it can do, but how does ChatGPT actually work? While the details of its inner workings have not been published, we can piece together its functioning principles from recent research.

    News, Tutorials, AI Research
  • QA_PRO | Тестирование

    🤷‍♂️ Social engineering?