Skip to main content

Provenance & Profiling

Is your car German or Japanese? Are your chocolates from Belgium? And your wine, which country might that be from? There's a good chance you know the answer to some of those questions. Our culture places value on provenance. That is, we care where our possessions originate. It's something we tend to notice.

Warning label?

Furthermore, we ascribe, often without our notice, characteristics to things because of their provenance. For example, that's a Japanese radio - its reliable but not cheap, etc. I often do this un-empirically, without measurement or examination. (that's a flaw)

For software testing, our automatic identification of provenance can be both a useful tool and a distraction. 

Noticing where or from whom a feature originated can be enlightening. You may learn over time that a particular team or person tends to implement certain things well, and others things not so well.

This has a tendency to help me to find some bugs relatively easily with individual teams. The first time it may have been time-consuming to see an issue. On subsequent releases, annoyingly easy.

That emotion is useful. Its an indication that you have, maybe subconsciously,  profiled the team. You can direct your response to that feeling, in constructive ways. For example, searching for a route cause or suggesting the addition of some unit tests.

It can be useful to think and deliberate over how you may have profiled the teams or people. Again, this is valuable 'intelligence,' the profile can help with planning your time and focusing test automation efforts. Though, the pattern also embodies a form of bias. You should be aware that you are subject to this bias, and routinely double check your assumptions.

It would be easy to concentrate too long on easy to find - known unknowns that were easy to spot thanks to your biased view. To increase our opportunities for discovering new types of issues, set aside time for investigating the app in other ways. 

Comments

  1. Hello people! Our company https://expertpaperwriter.com/enotes-review/ never doubt the quality of our content. But if you do, a refund is guaranteed. To ensure 100% uniqueness of your review, experts examine the final copy using advanced tools. Top-quality is a must. A team of professional editors re-check your order before delivery.

    ReplyDelete

Post a Comment

Popular posts from this blog

Betting in Testing

“I’ve completed my testing of this feature, and I think it's ready to ship” “Are you willing to bet on that?” No, Don't worry, I’m not going to list various ways you could test the feature better or things you might have forgotten. Instead, I recommend you to ask yourself that question next time you believe you are finished.  Why? It might cause you to analyse your belief more critically. We arrive at a decision usually by means of a mixture of emotion, convention and reason. Considering the question of whether the feature and the app are good enough as a bet is likely to make you use a more evidence-based approach. Testing is gambling with your time to find information about the app. Why do I think I am done here? Would I bet money/reputation on it? I have a checklist stuck to one of my screens, that I read and contemplate when I get to this point. When you have considered the options, you may decide to check some more things or ship the app

XSS and Open Redirect on Telegraph.co.uk Authentication pages

I recently found a couple of security issues with the Telegraph.co.uk website. The site contained an Open redirect as well as an XSS vulnerability. These issues were in the authentication section of the website, https://auth.telegraph.co.uk/ . The flaws could provide an easy means to phish customer details and passwords from unsuspecting users. I informed the telegraph's technical management, as part of a responsible disclosure process. The telegraph management forwarded the issue report and thanked me the same day. (12th May 2014) The fix went live between the 11th and 14th of July, 2 months after the issue was reported. The details: The code served via auth.telegraph.co.uk appeared to have 2 vulnerabilities, an open redirect and a reflected Cross Site Scripting (XSS) vulnerability. Both types of vulnerabilty are in the OWASP Top 10 and can be used to manipulate and phish users of a website. As well has potentially hijack a user's session. Compromised URLs, that exp

DevOps and Software Testing.

Most of my recent work has been with DevOps teams. While in one sense DevOps is another evolution in software development. It also introduces some new skill requirements and responsibilities into the daily routine of a tester. These diagrams tend to confuse people, hence the video... I've created a short video to highlight some of these changes and the opportunities they bring. It's not an exhaustive view of DevOps but it gives a highlight of what you could be working with. While DevOps isn't a panacea to our software development problems, I have found that empowering teams with the ability to build and use the tools they need, can rapidly improve team morale and productivity.