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

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

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

he icon   en icon

בכדי לכתוב בפורום יש להרשם או להתחבר - ההרשמה/כניסה מתבצעת מכותרת האתר.  

ברוך הבא, אורח
שם משתמש: סיסמה: זכור אותי

פרופיל משתמש halperinko

halperinko's Avatar
  • מנותקים
  • דירוג: Administrator
  • תאריך הרשמה: 25 דצמ 2011
  • תאריך כניסה אחרון: 18 נוב 2019
  • זמן: GMT +0:00
  • זמן מקומי: 15:28
  • פוסטים: 836
  • תודות שהתקבלו 35
  • צפיות בפרופיל: 744
  • קארמה: 3
  • מיקום: Unknown
  • מגדר: לא ידוע
  • תאריך לידה: Unknown



פוסטים אחרונים

אין פוסטים

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

  • Practical test strategy for Spring & React application

    Practical test strategy for Spring & React application Contents:1) Introduction2) System overview3) Functional test strategy4) Non-functional test strategy1. IntroductionThere are two leading approaches for tests: isolated and end to end (E2E). As usual, both approaches have upsides and downsides and it's impossible to say which one is better. Everything is dependent on application context and architecture.There are though few guidelines which can be followed most of the time:high test coverage should be achieved for a single application. Other parts of the system (i.e. connected microservices) should be stubbed/mockedimportant business cases should be tested in the E2E manner without any mocks. E2E tests should give us a high amount of confidence that our system will work on the productionisolated tests should make up the majority of your overall test countE2E test count should be low because they may be flakyIt remains to be seen whether or not contract tests would make a list of best practices. I certainly recommend adding them to the list.Enough of theory, let's move into applying it in real life.2. System overviewLet's say we want to test a very simple system with:a) Spring Boot backend b) React frontendTo complicate things a bit let's also assume that our backend is interacting with external API served by the other service (which we have limited control of).The application I wrote is very simple, it only allows to CRUD (create, read, update, delete) a user but it's about to overcome Facebook soon as the most popular social media platform so we need to prepare a comprehensive test strategy.3. Functional test[…]

    18.01.2020 | 6:47 קרא עוד...
  • Say It Out Loud - it’s Testing

    Sitting in front of they're computer, with a focused expression on their face, the tester is testing a new feature. Armed with their notes from all the whiteboard sessions, from design review and passing by comments of what we're changing and whatever requirements documentation they have, they've built their own list of functions they are about to verify that exist and work as expected."Error handling" says one of the lines in the functions list. Of course, every feature we implement should have error handling. Into the user interface fields where a sum of money is expected, they type away things that aren't numbers and make no sense as money. With typing of "hundred" being ok'd and just saved away to be reviewed later, it is obvious that whatever calculations we were planning to do later to add things up will not work, and armed with their trusty Jira bug reporting tool, they breathe in an out to create an objective step by step bug report explaining that the absence of error reporting is indeed a bug.Minutes later, the developer sharing the same room just pings back saying the first version did not yet have error handling implemented. The tester breathes some more.---The thing is, errors of omitting complete features are very common finds for us testers. Having found some thousands of them over my tester career, I'm also imagining I see a pattern. The reactions to errors of omitting complete features very often indicate that this did not come as a[…]

    18.01.2020 | 4:49 קרא עוד...
  • Burned by Thunderbird 68? Here’s How to Get Your e-mails Back!

    One of my "Randy-isms" is "Just because you are ready to release the code doesn't mean the user is ready to accept it."That played out for me today when I opened Thunderbird for Mac and it auto-installed the most recent release (68.4.1).Immediately, I noticed all my e-mail accounts and e-mails within them were gone, gone, gone. Deep breaths....So, I looked into this release and saw, "Thunderbird version 68.4.1 provides an automatic update from Thunderbird version 60." However, that was not the case for me and I suspect it may not be the case for others.You must understand that I don't do "Inbox Zero". In fact, my inbox is my history for many things I do (along with the thousands of pictures on my phone). So, I was somewhat panicked.However, I knew the e-mail files were there, just not being seen by the new version. Plus, I have redundant backups, so I knew I could get everything back. And...the beauty of the Mac is that you can just run the app with no install process like in Windows.I managed to find the old version at https://ftp.mozilla.org/pub/thunderbird/releases/I downloaded version 60.9.1 (you will need to navigate through the sub-folders to get the right language version).I opened it and instantly had access to all my e-mails.The new version (68.4.1) looks great, but it was useless to me. I hope it works for me better in future releases. But for now, I have "auto update" turned off!I hope this helps you!

    17.01.2020 | 12:56 קרא עוד...


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