LOGIN
התחברות או הרשמה
להמשך הרשמה ידנית – לחץ על כפתור ההרשמה, להרשמה/כניסה מהירה בעזרת חשבון רשת חברתית – לחץ על הלוגו בכותרת
A tester on a community I belong to recently asked whether we find bugs by design or by accident more fulfilling. Here’s my response: I am not sure there is a “by accident” in testing. If you set out to do something, and you discover something else along the way… before you even got to the feature you set out to test, that is a valid find. And part of a failure of the preconditions for the test you expected to run (whether or not that test actually had tests formally planned). In 16 years of testing I never defined or planned HOW I was going to test, I had a vague idea of what it was meant to do and how I would get there to do it. I never wrote test cases in advance. It was contextual. And find bugs I did. In, on, and around the thing I wanted to test. None of which would have been found by code. Because code can’t explore or evaluate the importance of bugs, and would fail if the journey to the feature was unavailable. I’d say 50% of my testing experience was feature-testing related, and 50% was “stuff I found while getting to the feature or other stuff in the feature that wasn’t expected.” I didn’t answer which is more enjoyable, come to think of it, because it was all enjoyable for me, and all equally valuable.
18.08.2022 | 8:59 קרא עוד...
The recording of my live coding YouTube stream "API Testing mit Karate (API testing with Karate)" is now available (German only)! This was a 75 minute event in collaboration with Never Code Alone.
plugin:youtube
The (best) five blogs we can read today. Check them out. Meet The New Automation Question, Same As The Old Automation Question Written by: Paul Grizzaffi Customer-Centric Test Automation Approach Written by: Enrique A Decoss The Top Reason People Fall Short of Their Goals Written by: Frank Sonnenberg Microsoft Disrupts Russian Cyber-Espionage Group Seaborgium Written by: Phil Muncaster Design Patterns for QA Automation: Build effective test solutions Written by: Kostiantyn Teltov Quote of the day: “Sometimes we figure things out, and then life changes and we have to figure it all out again.” -Renee Carlino You can follow this page on Twitter
18.08.2022 | 12:21 קרא עוד...Oftentimes, it becomes necessary for Software Testing leaders to impress the importance of Software Testing with the business. It is not an easy task, as Software Testing is perceived to be a scripted execution of laundry list of checks to be executed, either by a machine or humans. Most of the times, it is trivialized that ‘testing’ could be done by automated checks in the pipeline and we are done with it, but that is neither what Software testing is nor the value it provides. Hence it is important to know the key points that you would have as part of your elevator pitch for Software Testing to your business. As with elevator pitch, you got to deliver your bullets quick and in a fashion that would convince a business to follow-up on it, to research more on it to see if and to what extent testing is required for their context. Here are two major points that I would have: The Software claims that it would do what it is supposed to do, in a way that it is supposed to do. But do we know for sure that that’s the case? Most of the times, it does not, irrespective of developer-driven checks, bells and whistles. We need validation and verification through human oversight, both while the product is being is built and after the product is deemed ready for shippingAutomation cannot check all the possible combinations, not because the resources are not available, but because it blindly executes[…]
18.08.2022 | 12:08 קרא עוד...The (best) five blogs we can read today. Check them out. Leadership Trust: Leaders, Are You Squandering It? Written by: Kate Nasser Innovations in Software Testing Written by: Natalie Rodgers Remote work is probably hurting your body and brain—but there are simple ways to fight it Written by: L’Oreal Thompson Payton Giving Good Feedback: Consider The Ratio Written by: Charity Majors Starlink Successfully Hacked Using $25 Modchip Written by: Elizabeth Montalbano Quote of the day: “So here I am. This is as good as it gets. Take it or leave it.” -Chuck Palahniuk You can follow this page on Twitter
17.08.2022 | 1:26 קרא עוד...Scenario Based Manual Testing Interview Questions and Answers: In this video we are going to discuss Scenario Based Manual Testing Interview Questions and Answers which you may face in your next interview. 👉Become a Software Tester even as a Fresher. https://thetestingacademy.com Scenario Based Manual Testing ... Read more The post REAL LIFE Scenario Based Manual Testing Interview Questions appeared first on Software Testing & Automation.
17.08.2022 | 12:39 קרא עוד...In this video, we are going to learn about the How to crack any Manual Testing Interview. We will discuss the Manual Testing Process, Projects and Things you should Know before Interview. 👉Manual Tester Blueprint Live Classes https://sdet.live/manual 👉 Download Manual Testing Templates ✅ Test ... Read more The post How to Crack Any Manual Testing Interview appeared first on Software Testing & Automation.
17.08.2022 | 12:33 קרא עוד...In this video, we are going to learn about the How to crack the Manual Testing Interview. We will discuss the Manual Testing Projects Questions. I will share the Handy things that you need to have in your PC to crack Manual Testing easily. 👉Manual ... Read more The post Sure Shot Way to Crack Manual Testing Interview appeared first on Software Testing & Automation.
17.08.2022 | 12:29 קרא עוד...In this video, we are going to learn about the 5 common Types of Software Testing for Interview. ✅ Want to Switch from Manual to Automation Testing – https://sdet.live/become ✅ Expectation from QA for API Testing Interview QnA 🔥 Notes Download – https://sdet.live/notes ✅ Resources ... Read more The post 5 Common Software Testing Types Explained in 7 minutes appeared first on Software Testing & Automation.
17.08.2022 | 12:25 קרא עוד...Automation Testing Made Easy Tools Tips & Training Can You Use Selenium Testing for API Testing? One question that came up during this year's Automation Guild session on Testing RESTful APIs with Rest-Assured with Bas Dijkstra was whether you can use Selenium for API testing. This is actually a question that, surprisingly, I get asked all the time. But I liked Bas's answer in our TestTalks interview and during the Automation […] You’re reading Can You Use Selenium Testing for API Testing?, originally posted on Automation Testing Made Easy Tools Tips & Training - Helping you succeed with all things software test automation performance & security and copyrighted by Joe Colantonio
16.08.2022 | 11:56 קרא עוד...It has been a long struggle for 35+ years for the Software Testing field in trying to imitate humans in navigating the graphical user interface using automation scripts. There have been some advances, but essentially, we are still pretty much standing at the same place today doing one of these three methods: Specify expectations through a human-friendly language Have a higher level of abstraction and then generate scriptsHave the engineers write and maintain the scripts One way of the other, if you are required to tell the computer about what to expect, you are bound to one of the above. Nothing wrong with that, except that the cost of maintenance is high in terms of human effort and energy and the amount of time taken. The whole idea of automating is to reduce human fatigue, but if you are tinkering your automation script on a Friday evening for a Monday release instead of going home and being with the family, then you have not achieved your objective. There should be an alternate approach to automation, one that does not involve trying to imitate human actions. I am not talking about model-based testing or AI-based exploration, as these have their own problems too. I am thinking automation should be placed in a difference context altogether. Automation is necessary; it cannot be done away with. We got to look at how to use it effectively for our purposes. I have some thoughts. They need to be solidified. I am working on them.[…]
16.08.2022 | 11:52 קרא עוד...Automation Testing Made Easy Tools Tips & Training How to Perform Web Service Testing: The Definitive Guide As more and more businesses move to the web, the need for robust and dependable web services also grows. But how can you be sure your web service is up to par? Web Service Testing is essential. Whether you're a developer building web services for the first time or an experienced tester, this guide lays […] You’re reading How to Perform Web Service Testing: The Definitive Guide, originally posted on Automation Testing Made Easy Tools Tips & Training - Helping you succeed with all things software test automation performance & security and copyrighted by Joe Colantonio
16.08.2022 | 11:45 קרא עוד...Automation Testing Made Easy Tools Tips & Training 15 Reasons Why You Should (or shouldn’t) Automate a Test Just because you can automate something doesn’t necessarily mean that you should. In some cases, it might be more beneficial to use manual testing to test several aspects of the project accurately. In this post, you’ll learn: some factors to consider to help determine which manual tests should or should not be automated several guidelines […] You’re reading 15 Reasons Why You Should (or shouldn’t) Automate a Test, originally posted on Automation Testing Made Easy Tools Tips & Training - Helping you succeed with all things software test automation performance & security and copyrighted by Joe Colantonio
16.08.2022 | 11:21 קרא עוד...Here is a collection of free software testing programmes that I am aware of. Please note that by “free” I mean there is no upfront cost to enroll, but for some of them, you may have need to work at their company for a specified period of time or pay a fee if you leave too early. A software testing programme, is where you can learn to become a software tester as part of a structured programme.
16.08.2022 | 12:46 קרא עוד...
In 1971, The Who released the single Won’t Get Fooled Again from their upcoming album Who’s Next. Fast forward to 2002 when this tune was introduced to a new set of listeners as the opening theme to CSI: Miami (cue witty remark by David Caruso’s Horatio Caine).
Apart from the sheer rock-and-roll brilliance of this song, I’ve always been drawn to the lyric “meet the new boss, same as the old boss”. This lyric strikes me as both poignant and revelatory: sometimes, a new thing ends up being basically the same as the previous thing. It’s come up many times in my life and my career. I frequently quote it when I’m experiencing the “same old situation, yet again”.
This is particularly true with questions I see about choosing a test automation tool.
Back around 2014, I created a talk inspired by questions I saw in LinkedIn automation and testing groups. Many of the questions started with a phrase similar to “What’s the best tool for…”. Now, don’t get me wrong, there’s nothing wrong with asking questions, not even these kinds of questions. The challenge we face with these questions is the lack of context; without at least some context, it’s extremely to give responsible guidance. What’s worse, in my opinion, are the answers that I’ve seen. One word/phrase answers like “Selenium” or “Playwright” by supposed experienced colleagues can inadvertently lead the question asker down a path that is inappropriate for them, though it might be totally appropriate for the[…]
DAST stands for “Dynamic Application Security Testing” , it means analyzing a web application through the front-end to find vulnerabilities through simulated attacks. This type of approach evaluates the application from the “outside in” by attacking an application like a malicious user would.
In this kind of testing you can try attacks like SQL injection , XSS attacks , CSRF attacks , Source code disclosure and more..
The difference between DAST and Static analysis are the following :
You don’t need an access to the source codeAttacker does not require to have any prior knowledge about the system or the applicationThat is somehow a simulation to what an outsider attacker may do.
Tools :
HCL AppScanOWASP Zap (also known as Zap Poxy)Fortify Web InspectBurpSuite
Only Zap Proxy is the free tool within the list , but for AppScan you can download the demo version and try it against “Altoro Mutual (testfire.net)“
Example :
We’re going to use OWASP Zap to demonstrate a quick example.
Zap has 2 types of attacks :
Automatic attack , and here you only provide the application url , the tool crawl/spider the application and then run some attacks against the discovered pages.Manual attack , and here you are browsing the application manually and use it as a normal user , you can login , register , submit form or any other functionality available on the application.The benefit here that you can access some pages or functions that the automatic attack can’t , like all the[…]
The (best) five blogs we can read today. Check them out. Microsoft: We Don’t Want to Zero-Day Our Customers Written by: Jai Vijayan Two Breakthrough Questions That Change The Way People Think Written by: Dan Rockwell Code Coverage Vs Test Coverage Written by: Kavitha Rajagopal Why Automate Tests In An Agile Environment? Written by: David Tzemach USB Forensics – Reconstruction of Digital Evidence from USB Drive Written by: Bala Ganesh Quote of the day: “I want to do things for people they will never forget. Maybe that’s the best thing I can do in life.” -Simon Van Booy You can follow this page on Twitter
16.08.2022 | 1:09 קרא עוד...Automation Testing Made Easy Tools Tips & Training Headless Testing Awesomeness: Pros and Cons What is Headless testing? As the web evolves, new technologies are born, and others fall into obscurity. Headless browser testing is one of those technologies that has been on the rise in recent years. But what is this headless testing “browsing”? It actually is what it sounds like. Headless testing is when you run a […] You’re reading Headless Testing Awesomeness: Pros and Cons, originally posted on Automation Testing Made Easy Tools Tips & Training - Helping you succeed with all things software test automation performance & security and copyrighted by Joe Colantonio
15.08.2022 | 11:56 קרא עוד...Automation Testing Made Easy Tools Tips & Training What is Throughput in Performance Testing? Throughput is one of the most misunderstood performance testing concepts new testers sometimes struggle with. So what is throughput? Here are the three best definitions of throughput: Basically, “Throughput” is the number of transactions produced over time during a test. It’s also expressed as the amount of required capacity that a website or application can […] You’re reading What is Throughput in Performance Testing?, originally posted on Automation Testing Made Easy Tools Tips & Training - Helping you succeed with all things software test automation performance & security and copyrighted by Joe Colantonio
15.08.2022 | 11:26 קרא עוד...There was an interesting topic that was brought up on Software Architecture yesterday in LinkedIn. As always, new keywords keep coming up in the Software arena, and the one that I encountered yesterday was ‘Architecturally Significant Requirements’, which had been coined in 2016. The definition of ASR seems pretty straight-forward, although it would be difficult to find out which requirements are architecturally significant, and if there are any hidden requirements in the existing requirements that are architecturally significant. This is a good challenge to have for a Software Testing professional, as they are well-placed to dig out and detect these kind of stuff when they learn about the software. The indications of whether a requirement is an ASR as per Wikipedia are: Associated with high business value and/or technical risk.A concern of a particularly influential stakeholder.Has a first-of-a-kind character, e.g. none of the responsibilities of already existing components in the architecture addresses it.Has QoS/SLA characteristics that deviate from all ones that are already satisfied by the evolving architecture.Has caused budget overruns or client dissatisfaction in a previous project with a similar context. Sounds familiar? To me, there were many requirements like that during my course of testing systems software and applications, especially in the areas of performance (e.g. application support for 100,000 devices!). The process of finding out whether the software would satisfy such a requirement (which would blow the existing design) is excruciatingly slow, which often involves multiple iterations of testing. ‘Go step by step’, the developers would advice,[…]
15.08.2022 | 9:01 קרא עוד...
A tester on a community I belong to recently asked whether we find bugs by design or by accident more fulfilling. Here’s my response: I am not sure there is a “by accident” in testing. If you set out to do something, and you discover something else along the way… before you even got to the feature you set out to test, that is a valid find. And part of a failure of the preconditions for the test you expected to run (whether or not that test actually had tests formally planned). In 16 years of testing I never defined or planned HOW I was going to test, I had a vague idea of what it was meant to do and how I would get there to do it. I never wrote test cases in advance. It was contextual. And find bugs I did. In, on, and around the thing I wanted to test. None of which would have been found by code. Because code can’t explore or evaluate the importance of bugs, and would fail if the journey to the feature was unavailable. I’d say 50% of my testing experience was feature-testing related, and 50% was “stuff I found while getting to the feature or other stuff in the feature that wasn’t expected.” I didn’t answer which is more enjoyable, come to think of it, because it was all enjoyable for me, and all equally valuable.
18.08.2022 | 8:59 קרא עוד...
The recording of my live coding YouTube stream "API Testing mit Karate (API testing with Karate)" is now available (German only)! This was a 75 minute event in collaboration with Never Code Alone.
plugin:youtube
The (best) five blogs we can read today. Check them out. Meet The New Automation Question, Same As The Old Automation Question Written by: Paul Grizzaffi Customer-Centric Test Automation Approach Written by: Enrique A Decoss The Top Reason People Fall Short of Their Goals Written by: Frank Sonnenberg Microsoft Disrupts Russian Cyber-Espionage Group Seaborgium Written by: Phil Muncaster Design Patterns for QA Automation: Build effective test solutions Written by: Kostiantyn Teltov Quote of the day: “Sometimes we figure things out, and then life changes and we have to figure it all out again.” -Renee Carlino You can follow this page on Twitter
18.08.2022 | 12:21 קרא עוד...
אל תשאירו Bug validation לסוף הגירסה - טפלו מוקדם ככול האפשר, אח"כ הם מצטברים ולא נותר זמן לטפל. באגים נוהגים להתקבץ - גם במקרה הפחות נפוץ שהבאג אכן טופל עם כל ההשפעות שציינתם :-), דיי סביר…
"בדוק מוקדם ככול הניתן" – אחת המטרות של הבדיקות הינה לספק כמה שיותר משוב ומידע לגבי איכות המערכת מנקודות מבט שונות (פונקציונליות ולא פונקציונליות כמו עמידה בעומסים ושאר יכולות). לעיתים בודקים נוטים בטעות לחשוב כי הדרך…
