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

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

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

he icon   en icon

RSS מהעולם

  • 10 things I learned from my first two weeks as a Peloton bike owner

    10 things I learned from my first two weeks as a Peloton bike owner TL;DR - I'm feeling healthier, happier and more engaged with my fitness - but I've quickly learned to adjust some of my expectations! 🚴‍♂️ After 18 months of having a membership to a gym which was closed for a year, with autumn and winter fast approaching, and with the desire to kickstart my 40s with a big fitness push, I recently took the plunge and invested in a Peloton bike (a decision which was helped by a recent price reduction, as well as Postman giving employees a sizable rebate on fitness/wellness equipment). Fast-forward just over a fortnight, and I've already notched up over 500 miles in the saddle, and should be hitting my "100 rides" milestone in the next few days! During the frenzied first couple of weeks, I've slowly learned to slightly adjust what I thought the Peloton experience would be like, versus what it actually has been like. I've had a few people asking for insider tips on social media, so as usual, I've written down more than you could possibly want to know. If you find the below tips useful, and particularly if you end up purchasing a Peloton product off the back of it, I'd be hugely appreciate if you used my referral code 73U5JX at checkout. It'll give you £100 off any accessories that you purchase at the same time as the bike, and it'll give me a £100 voucher for the Peloton apparel store (and frankly, their clothing ain't the cheapest). #1: Do your[…]

    24.09.2021 | 4:30 קרא עוד...
  • Five for Friday – September 24

    Back for another week of random links and interesting articles from the internet. For the ‘murican readers here, the US Vaccine Tracker is a nice look at vaccine rates across a variety of demographics.A great article on metrics that don’t suck from Greg PacigaJust this week, I was in a conversation about automating development environment setups…and then I also run into this article on the subject (and a pointer to gitpod).It’s been a while since I’ve pointed to the Netflix Tech blog, but there’s a nice article on A/B testing (with the slash) this week.Finally – I found this article on how the new generation of college students thinks about files and folders fascinating. If you’re my age, you may find it interesting too. See you next week.

    24.09.2021 | 12:15 קרא עוד...
  • Cypress Tutorial | How To Organize Cypress Test

    In this Cypress tutorial we are going to talk about test structure, how to organize cypress tests. Let’s open a new blank test file exampleTest.spec.js In each spec file, you should start with set in the first row the reference command /// <reference types="cypress" /> This command will give your cypress test autocomplete power and will help you to code faster. Mocha Mocha is a feature-rich JavaScript test framework running on Node.js and in the browser, making asynchronous testing simple and fun.Mocha tests run serially, allowing for flexible and accurate reporting while mapping uncaught exceptions to the correct test cases. Mocha, provides describe(), context(), it() and specify() blocks.context() is identical to describe() and specify() is identical to it(), so choose whatever works best for you. I work with the describe() and it(). Describe() Block In the describe() you provide the general description of what your test will be about.Then you open a callback function with curly braces and this will create the body when you will insert the tests. describe('this is a describe block', () => { }) Create it() block inside the describe, this block is the test case where you type the actual test code.In the result, you will see that the test case demo was executed and the name of the test was test case demo. describe('this is a describe block', () => { it('test case demo', () => { }); }) This is the most simple structure, how the test should be organized inside the spec file.You can put as many tests as you want inside the describe block. describe('this is a[…]

    24.09.2021 | 11:44 קרא עוד...
  • Is it possible to improve the impact of our Testing by simplifying it?

    I admire the simplicity of TDD. Red, Green, Refactor. Write a test, see it fail. Write some code, see the test pass. Refactor your code, the test should still be green. It’s simple to describe and a simple concept to understand. Except it’s not simple. I rarely practice TDD by myself these days, but I clearly remember how hard it was first picking it up. It took a lot of frustration and failure to get to a point where I felt comfortable. Compare that to Testing. Testing is hard, just like TDD. Testing also feels hard to understand. There’s Strategies, Plans, Frameworks, not to mention the nebulous nature of knowing what and what not to test. You might’ve worked with a great software tester. As with all experts, great practitioners will make things look and feel simple, but they will all tell you that it’s not. For a long time I’ve been thinking about how I could simplify my testing world. To make it easier for me to hone my own craft and if possible, help those I work with get over that initial barrier. This is where I’ve got to. Explore, Act, Improve. Explore ‘something’ to gain knowledge. Use the knowledge to act. Improve how we explore. The current working title for this process is Action Driver Exploration. Better suggestions are very welcome! Déjà vu As with all things, nothing is truly new. As I’ve gone through my career I’ve reached points I might classify as step-changes in my[…]

    24.09.2021 | 11:03 קרא עוד...
  • Lots of new blogs, podcasts, videos to share!

    Lots of new blogs, podcasts, videos to share! Hi friends! I haven’t posted here for a long while, because I’ve spent my time co-writing blog posts with Janet Gregory on our Agile Testing Fellowship blog. We also write our monthly newsletter with exclusive content, please subscribe if you haven’t already! Most excitingly, Janet and I record monthly 15 minute video chats on our YouTube channel, and inviting leading practitioners to join us occasionally. I’ve also been totally absorbed by my new job, which I started in January. I’m a hands-on tester on a team and I have been spending time learning so I can contribute more. Practicing some basic coding skills, learning how to use new-to-me monitoring and observability tools, learning a complex business domain. So, not so much time to write and speak. I do have some talks coming up in October. Recently I had the great opportunity to talk with Len Epp, co-founder of LeanPub, on his FrrontMatter podcast. We had a terrific conversation which ranged from explaining agile concepts to the kind of work I do with my donkeys! You can subscribe to his podcast on your podcast app of choice. You can also listen or read the transcript on the podcast website. He’ll be interviewing Janet soon, and he’s interviewed many of my favorite LeanPub authors already. Highly recommended! The post Lots of new blogs, podcasts, videos to share! appeared first on Agile Testing with Lisa Crispin.

    24.09.2021 | 9:16 קרא עוד...
  • Five Blogs – 24 September 2021

    The (best) five blogs we can read today. Check them out. Learning with an Expert Written by: Bill Wake Building a secure application in five steps Written by: Vickie Li Our Brains Were Not Built for This Much Uncertainty Written by: Heidi Grant and Tal Goldhamer Why Blog Post Titles Are Crucial Written by: Darren Rowse Ransomware now accounts for 69% of all attacks that use malware Written by: Lance Whitney Quote of the day: “I want to be able to trust, not live in perpetual self-defense.” -Anaïs Nin You can follow this page on Twitter

    24.09.2021 | 1:39 קרא עוד...
  • macOS vs Ubuntu Linux Part 2

    macOS vs Ubuntu Linux Part 2 Introduction In macOS vs Ubuntu Linux I’ve written about a fun experiment. I’ve dual booted an MacBook Air with macOS and Ubuntu. Then, I ran the same npm scripts on both operating systems. To make things more interesting, I’ve ran the scripts both on the host operating system and inside a Docker container. Running scripts on Ubuntu was so faster, that I wanted to dual boot my iMac too. At the time, I could not dual boot the iMac because my disk refused to be partitioned. In the last couple of weeks, I’ve formatted disks on both machines and did a clean install of both macOS and Ubuntu. It’s time to run the experiment again! Machines For reference, here’s the table with the two machines and the Fresh container, with some relevant data. Machine iMac 13,2 (27-inch, 2012) MacBook Air 6,1 (11-inch, 2014) Fresh Processor 3,2 GHz Quad-Core Intel Core i5 1,4 GHz Dual-Core Intel Core i5   RAM (GB) 16 4   macOS 10.15.7 11.6   Linux Ubuntu 21.04 Ubuntu 21.04 Debian 9 (stretch) Docker 20.10.8 20.10.8   Docker Compose 1.29.2 1.29.2   Fresh 21.04.1 21.04.1   Node.js 10.24.1 10.24.1 10.15.2 npm 6.14.12 6.14.12 6.14.5 MediaWiki 1.38.0-alpha 1.38.0-alpha   Chrome (macOS) 94.0.4606.61 94.0.4606.61   Chromium (Linux) 93.0.4577.82 93.0.4577.82 73.0.3683.75 Docker I’ve left Docker settings at default values. Increasing resources available to Docker might speed things up on MacOS, but that’s a topic for another blog post. For my reference, here are the default values in Docker Preferences > Resources[…]

    23.09.2021 | 7:00 קרא עוד...
  • Using Triforce to define Acceptance Criteria

    Using Triforce to define Acceptance Criteria Acceptance Criteria (ACs) are the basics for providing the “what” for any business ask. At their core they are a series of functionality statements telling us what behaviours we want from a feature and link the business ask back to engineering. As testers we use the Acceptance Criteria to help guide our testing and can even push our testing to the left (earlier) by helping to refine the ACs to think about errors and edge cases. How do we do that? Using Triforce! What is Triforce? Triforce are sessions used to refine and create User Stories to provide a shared and complete understanding of what is to be built. You might have seen these sessions named Three Amigos or Power of Three; I call them Triforce because 1) That’s an non-gendered name and 2) It sounds cool and fun to be a part of. They are a collaboration between project team members who each champion a perspective needed: Business, Engineering & Testing. Business – provide context on requirements and user needs (e.g. product owner / product designers).Software engineering – provide context on implementation details and what’s possible.Testing – seek to ensure tickets are testable and ready for development by ensuring all thoughts are covered. The Tri in Triforce does not refer to the number of people in a session, it refers to the number of perspectives (or hats) that should be represented in a session. Given that there may be people with different amounts of domain knowledge or front end[…]

    23.09.2021 | 8:43 קרא עוד...
  • Performance testing API’s with async/awaits

    Performance testing API’s with async/awaits I’ve got this serverless cloud function, you can read about how I built it here. Today’s blog is how I’d go about performance testing this API using async/awaits in Typescript. The API helper class Here is the GET API function: import request from 'supertest'; /** * Checks API is up. */ export async function checkMinSupportedVersionAPIReturns200( ) { const response = await request('https://australia-southeast1-buggybank.cloudfunctions.net/') .get(`min-app-version`) .expect(200); return response; } The performance test Here’s the performance test function, it spins up 10 concurrent instances to hit this API over 5 seconds. And it’ll wait 30 seconds before timing out. describe( 'performance test APIs', () => { it('should handle some load', async () => { await sendManyRequests(10, 5); }, 30000); Helper function – send single request There’s a send single request helper function, I really should have used another one with a shorter name but I’m a lazy dev. const sendSingleRequest = async (): Promise<void> => { await checkMinSupportedVersionAPIReturns200(); }; Helper function – send many requests Next thing to add is a function that calls many requests and builds up from that single request. Inflight is used to increase the await time. const sendManyRequests = async (maxInflightRequests:number, durationSeconds: number): Promise<void> => { let inFlight = 0; const startEpoch = Date.now(); const endEpoch = startEpoch + (durationSeconds * 1000); while (Date.now() < endEpoch) { while (inFlight < maxInflightRequests) { inFlight++; sendSingleRequest() .then(() => { inFlight--; }) .catch((err) => { inFlight--; console.error(`Request error: ${err}`); errorCount++; }); } await delay(10); } while (inFlight > 0) { await[…]

    23.09.2021 | 3:39 קרא עוד...
  • Podcast | API Testing Using Postman With Kristin Jackvony

    This API testing podcast definitely will help you out.In many ways, API testing is faster and far superior to automated UI Testing. Find out why In this episode. Kristin Jackvony, a software tester, blogger, and soon-to-be-published author, will share some key takeaways from her LinkedIn course on Postman Essential Training.For all your testers and developers that need to do API testing, you’re in for a treat. You’ll learn all about Postman, a popular (and free) solution, and how it can help you with all your API testing needs. Listen up! Check out our API Testing Articles The post Podcast | API Testing Using Postman With Kristin Jackvony appeared first on TestsVision.

    23.09.2021 | 2:48 קרא עוד...
  • Five Blogs – 23 September 2021

    The (best) five blogs we can read today. Check them out. Why quantum computing is a security threat and how to defend against it [Q&A] Written by: Ian Barker Transactive Memory and Agile: An Overview Written by: Thomas Cagley Anatomy of An Automated Test Script Written by: Heitor Paceli Key Metrics for Measuring Test Automation Success Written by: Raj Subrameyer The “Trigger” Strategy For Driving Radical, Transformational Change Written by: Greg Satell Quote of the day: “Life is irrational and we can’t grasp its reasons at times but one thing’s for sure everything that happens to you now is towards a purpose” -Gia Sison You can follow this page on Twitter

    23.09.2021 | 1:20 קרא עוד...
  • Five Blogs – 22 September 2021

    The (best) five blogs we can read today. Check them out. Page Object Model with Playwright Written by: Andrii Baidachenko How To Create Order And Efficiency In Your Business Written by: Chantal Bechervaise Six Leadership Steps When Feeling Blindsided Written by: Terri Klass How can a modern QA, break the silos between teams Written by: Rody Bothe Capping it Off Written by: James Thomas Quote of the day: “You do not have to be fearless just don’t let fear stop you” -Charlie Day You can follow this page on Twitter

    22.09.2021 | 1:36 קרא עוד...
  • Three ways to make metrics suck less

    Everybody loves to hate metrics. I get it. There are a lot of terrible metrics out there in the software development and testing world. People still propose counting commits or test cases as a measure of productivity. It’s garbage. But I also believe that measuring something can be a useful way to understand aspects of it that you couldn’t get with qualitative measures alone. I’m not going to give a defence of metrics in all cases here, but I do have a few suggestions for how to make them suck less. 1. Be very explicit about what a metric measures To take the example of counting the number of commits a developer makes. It’s a terrible metric because commits aren’t actually a measure of productivity. While the platonic ideal of a commit is that it represents a single atomic change, the amount of work involved could still involve anything from a single character change to a large refactor of a highly coupled codebase. Number of test cases run and the number of bugs found are equally bad metrics. Neither has an unambiguous way to be counted. Test cases can be broken up in all kinds of arbitrary ways to change their number. Meanwhile a single root cause might be reported as 8 different bugs across 3 application layers, either just because that’s how it manifested or because someone is incentivized to find lots of bugs. There’s a very academic but interesting paper by Kaner & Bond all about rigorously asking[…]

    22.09.2021 | 1:00 קרא עוד...
  • Agile Manifesto

    In this video, We are going to Learn about the Agile Manifesto, What are 4 important Set of values that they talk about, Important Exam question. This is Part of ISTQB Agile Tester Certification aka Certified Tester Foundation Level – Agile Tester ( ISTQB). ✅ ... Read moreAgile Manifesto The post Agile Manifesto appeared first on Software Testing & Automation.

    21.09.2021 | 11:34 קרא עוד...
  • Agile Software Development Explained

    In this video, we are going to start a new Series, We are going to explain, Agile Software Development in nutshell. This is Part of ISTQB Agile Tester Certification aka Certified Tester Foundation Level – Agile Tester ( ISTQB) Series Day 2 ✅ Download Notes ... Read moreAgile Software Development Explained The post Agile Software Development Explained appeared first on Software Testing & Automation.

    21.09.2021 | 11:28 קרא עוד...
  • Capping it Off

    Capping it Off I'm lucky that my current role at Ada Health gives me, and the rest of the staff, a fortnightly community day for sharing and learning. I've done my, erm, share of sharing, but today I took advantage of the learning on offer to attend a workshop on our approach to making medical terminology accessible to non-experts, a presentation on how we manage our medical knowledgebase, another on the single sign-on infrastructure we're using in our customer integrations, and a riskstorming workshop using TestSphere to assess an air fryer. So that would have been a great day by itself, but I, erm, capped it off by attending Capgemini's TestJam event, to see the keynotes by Janet Gregory and Lisi Hocke. Janet talked about holistic testing, or the kinds of critical review, discovery, and mitigation activities that can take place at any point in the software development (and deployment, and release) life cycle. The foundation for all of this is good communication and relationships between the people and teams involved, and she often sees testers being the ones to cultivate that. The key thing about a cycle is that there is no end. Release isn't where we wash our hands of the frickin' thing and relax, it's the point at which we can begin to observe what our customers are doing with it, and frame some hypotheses about how we could improve their experience. Testers should be here, framing experiments that feed into the next round of discovery that leads to planning[…]

    21.09.2021 | 3:31 קרא עוד...
  • APIs Unleashed 08: Handling GraphQL

    Exploring how to handle GraphQL using Postman and KarateDSLThe post APIs Unleashed 08: Handling GraphQL appeared first on Synapse QA.

    21.09.2021 | 10:15 קרא עוד...
  • How We Used Slack to Manage Testing Devices

    How We Used Slack to Manage Testing Devices Necessity is the mother of invention. Or in my case, pain is the mother of invention! I have roughly 50 QA devices I am responsibleContinue reading

    21.09.2021 | 9:04 קרא עוד...
  • Put The Mock Gun Away

    I gave a course recently on unit testing in Angular, and we were looking at some code the developers wrote, and we wanted to test. It looked something like this: someApiCallAsync(p1, p2, ...) .then(response => { if (response.ok){ .... } else { ..... }; }) Basically we’re looking at an async API call, and after it completes, we check the response and do something with it. The code uses the Promise construct in JavaScript, which is basically async / await in other languages. The discussion went in the direction of “how do we mock the API so it returns the status and body we want asynchronously”. Well, it’s easy to do with Jasmine spies. But is it necessary? What we really want to check is the behavior of the code after the async call was mad, which is in the then() block. The mocking is just a technique to get there. Instead, we can extract what’s inside the then() block to another method and test that one, without any mocking. Like this: function checkResponse(response => { if (response.ok){ .... } else { ..... }; }); Now we don’t need to mock anything, just check a simple function. Sometimes we need to remember what we want to check, rather than just go ahead using the mock gun. It can easily be done by simpler means. These are the things that I focus in my courses. Actual, useful, simple techniques to help you code and test better.  And on the code you[…]

    21.09.2021 | 2:21 קרא עוד...
  • Five Blogs – 21 September 2021

    The (best) five blogs we can read today. Check them out. API Security 101: Improper Assets Management Written by: Vickie Li There are Plenty of Ways to Talk about Exploratory Testing Written by: Maaret Pyhäjärvi Are You a Manager or a Leader? Written by: Steve Keating Writing Automated Tests in Small Increments Written by: Corina Pip Deep testing and “Deep Work” (Cal Newport) Written by: Lee Hawkins Quote of the day: “One form of perseverance is the daily discipline of trying to do things better than we did yesterday” -Angela Duckworth You can follow this page on Twitter

    21.09.2021 | 1:22 קרא עוד...

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

  • 10 things I learned from my first two weeks as a Peloton bike owner

    10 things I learned from my first two weeks as a Peloton bike owner TL;DR - I'm feeling healthier, happier and more engaged with my fitness - but I've quickly learned to adjust some of my expectations! 🚴‍♂️ After 18 months of having a membership to a gym which was closed for a year, with autumn and winter fast approaching, and with the desire to kickstart my 40s with a big fitness push, I recently took the plunge and invested in a Peloton bike (a decision which was helped by a recent price reduction, as well as Postman giving employees a sizable rebate on fitness/wellness equipment). Fast-forward just over a fortnight, and I've already notched up over 500 miles in the saddle, and should be hitting my "100 rides" milestone in the next few days! During the frenzied first couple of weeks, I've slowly learned to slightly adjust what I thought the Peloton experience would be like, versus what it actually has been like. I've had a few people asking for insider tips on social media, so as usual, I've written down more than you could possibly want to know. If you find the below tips useful, and particularly if you end up purchasing a Peloton product off the back of it, I'd be hugely appreciate if you used my referral code 73U5JX at checkout. It'll give you £100 off any accessories that you purchase at the same time as the bike, and it'll give me a £100 voucher for the Peloton apparel store (and frankly, their clothing ain't the cheapest). #1: Do your[…]

    24.09.2021 | 4:30 קרא עוד...
  • Five for Friday – September 24

    Back for another week of random links and interesting articles from the internet. For the ‘murican readers here, the US Vaccine Tracker is a nice look at vaccine rates across a variety of demographics.A great article on metrics that don’t suck from Greg PacigaJust this week, I was in a conversation about automating development environment setups…and then I also run into this article on the subject (and a pointer to gitpod).It’s been a while since I’ve pointed to the Netflix Tech blog, but there’s a nice article on A/B testing (with the slash) this week.Finally – I found this article on how the new generation of college students thinks about files and folders fascinating. If you’re my age, you may find it interesting too. See you next week.

    24.09.2021 | 12:15 קרא עוד...
  • Cypress Tutorial | How To Organize Cypress Test

    In this Cypress tutorial we are going to talk about test structure, how to organize cypress tests. Let’s open a new blank test file exampleTest.spec.js In each spec file, you should start with set in the first row the reference command /// <reference types="cypress" /> This command will give your cypress test autocomplete power and will help you to code faster. Mocha Mocha is a feature-rich JavaScript test framework running on Node.js and in the browser, making asynchronous testing simple and fun.Mocha tests run serially, allowing for flexible and accurate reporting while mapping uncaught exceptions to the correct test cases. Mocha, provides describe(), context(), it() and specify() blocks.context() is identical to describe() and specify() is identical to it(), so choose whatever works best for you. I work with the describe() and it(). Describe() Block In the describe() you provide the general description of what your test will be about.Then you open a callback function with curly braces and this will create the body when you will insert the tests. describe('this is a describe block', () => { }) Create it() block inside the describe, this block is the test case where you type the actual test code.In the result, you will see that the test case demo was executed and the name of the test was test case demo. describe('this is a describe block', () => { it('test case demo', () => { }); }) This is the most simple structure, how the test should be organized inside the spec file.You can put as many tests as you want inside the describe block. describe('this is a[…]

    24.09.2021 | 11:44 קרא עוד...

טיפים

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