LOGIN
התחברות או הרשמה
להמשך הרשמה ידנית – לחץ על כפתור ההרשמה, להרשמה/כניסה מהירה בעזרת חשבון רשת חברתית – לחץ על הלוגו בכותרת
עליכם להיכנס כמשתמשים רשומים בכדי להוסיף כתבות ומאמרים - ההרשמה/כניסה מתבצעת מכותרת האתר.
As I've mentioned in previous posts, this year I'm reading one testing-related book a month and reviewing it in my blog. This month I read Enterprise Continuous Testing, by Wolfgang Platz with Cynthia Dunlop.This book aims to answer solve the problems often found in continuous testing. Software continuous testing is defined by the author as "the process of executing automated tests as part of the software delivery pipeline in order to obtain feedback on the business risks associated with a software release as rapidly as possible". Platz writes that there are two main problems that companies encounter when they try to implement continuous testing:1. The speed problemTesting is a bottleneck because most of it is still done manuallyAutomated tests are redundant and don't provide valueAutomated tests are flaky and require significant maintenance2. The business problemThe business hasn't performed a risk analysis on their softwareThe business can't distinguish between a test failure that is due to a trivial issue and a failure that reveals a critical issueI have often encountered the first set of problems, but I never really thought about the second set. While I have knowledge of the applications I test and I know which failures indicate serious problems, it never occurred to me that it would be a good idea to make sure that product managers and other stakeholders can look at our automated tests and be able to tell whether our software is ready to be released.Fortunately, Platz suggests a four-step solution to help ensure that the[…]
In BDD workshops I briefly talk about feature slicing. In a nutshell:
Slice features so every feature should be deployable independently.
For this to happen, slice you features ‘across’ the tech stack, NOT ‘along’ the tech stack. (See attached images)
This is a common mistake, and seems easier to work that way.
For instance, develop the UI first, then the back end / business logic.
The problem here, your not deploying quickly / in small chunks.
Might as well call this waterfall development, because then that’s what this becomes..
#RedefiningSoftwareQuality #Agile #FeatureSlicing #AgileTransformation
The post Feature slicing across the tech stack appeared first on Quality Spectrum.
Dear Readers/Partners,Happy to announce the launch of India and Russia locale (in the Russian language) of 365NEWSX.All news related to India and Russia is aggregated from 500+ news sources, processed using TextRank and Sentiment AI algorithm so that we can bring the best of the best news and save your reading time. You can:Read your favourite news under 60 secs. Read-only important parts of a long news articleTake full control of your privacy and interestsBrowse India news under most popular category:PoliticsTechnologyScienceHealthEntertainmentCOVID-19Browse Russian news under most popular category:PoliticsTechnologyScienceHealthEntertainmentCOVID-19Please share this good news with your channels/friends/family/community.More locale coming soon - #Australia #Canada #Germany #France. Subscribe to our newsletter at: SUBSCRIBEEmail us your suggestions at info@365newsx.com=============================================Best Regards,Media Communication Teamwww.365newsx.com==============================================
אל תעשה משהו שמישהו אחר כבר ביצע - מבלי לשאול - למה צריך לעשות זאת עוד פעם? טיפים מחברי ITCB-AB
לא ניתן לבדוק את כל הקומבינציות - עשו ניתוח סיכונים בעיה ידועה בעולם הבדיקות היא - כי לא ניתן לבדוק את כל הקומבינציות של התכונות והערכים האפשריים ולכן עלינו לעשות ניתוח סיכונים סיכון - מהי חומרת הבעיה…
