Показ дописів із міткою english. Показати всі дописи
Показ дописів із міткою english. Показати всі дописи

понеділок, 30 жовтня 2017 р.

Expectations - Requirements - Reality

Recently, I once again saw the well-known Venn-diagram that is often used by Context-Driven Testing School adepts (this time at presentation at QA Fest 2017. Ilari Henrik Aegerter. What is Context- Driven Testing?). 
But I decided to improve it a bit.



Areas 4 + 7 + 5 + 2  - Written Requirements
Areas 1 + 4 + 7 + 6 - Customers' Expectations
Areas 6 + 7 + 5 + 3 - Actual Product
Only growing areas 6 and 7 will add value to the project and satisfy the business needs.


Let me explain this a bit to those who has not attended parties with participation of Context-Driven testers.

пʼятниця, 20 жовтня 2017 р.

Good Pyramid - Bad Pyramid

Along with awareness of the need to write automated tests, programmers are increasingly bogged down in the swamp of testers terminology (they think it's unified >: - E).
I decided to put some more historical context to the Pyramid understanding.

Just nice pyramids  from TUTORIAL 1 - OpenGL Fundamentals http://www.naturewizard.at/tutorial0104.html

QA battle at QAClubKiev: ISTQB - to be or not to be

Yesterday, there took place an event in a "pair competition" format or a public discussion, or even a "QA Battle"! This time with my participation. At this 19th QAClubKiev meeting, I tried to convince the audience and my dear opponent, Alexandra Kovalyova, that ISTQB Foundation Level certification is more harmful than useful. And in her turn, Alexandra tried to do the opposite.

VIDEO: The first 42m here (in Ukrainian)

вівторок, 7 лютого 2017 р.

Web Site UI Testing

"We were only changing the UI, so we don't need a full regression run here." - They said.

In Gerald Weinberg's "Secrets of Consulting" there was a wonderful chapter on "lullaby words". And "only" was one of them. Each time testers hear the word "only" - they start to get nervous. Or rather they smell bugs in the air :-)

I want to share my outlines that should be taken into account while testing "only UI" of a website (disregarding its platform or applied area).

понеділок, 16 січня 2017 р.

Being a Remote Tester

Being a people person, my first priority when seeking a new testing job always was a Team. Moreover, last couple of years I've been working in agile development team, mostly as a Scrum-master, with tight daily collaboration with developers (all sitting next to me) and whole-day-round chatting with a product owner (being remote but always available for any conversation during my working hours). I used to be aware of all processes and conversations going on in the team. I even could give a rough estimate instead of developers. Our team was really cross-functional and agile.
But the projects move in and out, companies grow and blow up.
So it was a time for me to move on. After almost a year of looking for a team/project that would be as good as the previous one, I gave up and accepted a proposal that made me an only team-member on the Europe continent with 10 hours time difference with the rest of the team. At that moment I truly felt what Gerald Weinberg puts in his Secrets Of Consulting: 
Struggling to stay at home can make you a wanderer.
Struggling to travel can make you a stay-at-home.

And I'm surprised how comfortable I am now in my new "stay-at-home" status!

http://thednetworks.com/wp-content/uploads/2012/03/under-sea-cable-map.png

вівторок, 29 листопада 2016 р.

Equivalence Class Partitioning - Explaining at Interview

More than a year ago, I went for an interview for a medical project. I was given some kind of a layout design and a product technical specification. The task was: "Describe your approach to the product testing, make use of Equivalence Classes Partitioning." I must admit that the layout design and specification prepared were very good for the purpose of a tester interview.
Although I knew what are "equivalence classes", and even had taught some theory to novice testers, the task made me stuck for a bit. After a pause (long enough to spoil the interview), I said:
- What should I break into Equivalence Classes? - Watching my competence decreases in the eyes of the interviewing Test Lead.

четвер, 24 листопада 2016 р.

Test Design Definition

There are numerous variants out there what exactly "Test Design" means.
Having tried to explain the matter several times lead me to the following definition which I find even more solid than my definition of testing.
This is how I put it:

Test Designing is prioritizing of an infinite list of all the possible inputs by the risk of not knowing the actual output.

I like this definition because:
  • it implements the agility of testing time-frames
  • its corner stone is risk - the main/only reason of doing testing at all
 And by inputs I mean everything that is needed for testing: data, steps, environments etc. And outputs are the system-under-test's reactions to our testing.

вівторок, 22 листопада 2016 р.

My definition of Testing


When I read the post in QA hiccaps: The Anatomy of a Definition of Testing, where James puts the following definition of Testing:  "Testing is the pursuit of actual or potential incongruity".
I find this definition rather romance. I think it was intentionally so.
I thought about how I understand the Testing in the whole its variety of actions, and came to the following definition:
 Testing is making implicit things explicit to someone who matters.
Why I find this definition important is that it does not include a person of a tester and does not insists the tester is right doing this "testing".
Because all humans, including testers are to err in directions of their "pursuit". I often find "incongruities" that appear not important, and if I had "pursued" them long enough I'd feel disappointed.
But when we report to someone who matters that there was something "implicit" for them, we let THEM decide if this info is useful, having done our part of the deal.
And with "implicit" I also mean "unconcious". What everyone look at but no one sees. The things that "a clear eye" can find.

PS Thus, my definition doesn't include testers, but instead includes those who are using information taken from testers. No, I don't find this fair. Here is a point for improvement :-)

неділя, 24 липня 2016 р.

"5 hours a day" keeps pressure away

A common question raised by customer-side management:

  • How to control software engineers? 
  • How I, as a customer who pays huge bags of cash per hour to this hippies, can really know that they are not cheating me watching youtube half a day?

But even if the question is not asked explicitly, does not mean nobody has doubts alike. 

I worked in various environments. Let me review the most common solutions and their pros and cons.





пʼятниця, 22 липня 2016 р.

Tester's mental "try ... catch"

Once this blog post http://www.inspiredtester.com/inspired-tester-blog/process-metrics-and-the-impact-of-context (and maybe a little bit of Jerry Weinberg's ideas) inspired me to this thoughts.




People like their "status Quo". They don't like to act. Every their action is forced by change. The change may be in outside, in circumstances; and it may be in themself. Changing the way one acts too is a reaction to different changes one experiences.

Applying this to the Software Testing, an experienced user becomes a tester, when they react not directly to external changes, but to the internal feelings induced by external changes. Establishing some kind of "try - catch" block for distractions in their brain. Instead of (or additionally to) just shouting out loud that "This piece of software does not work!", the tester asks themself: "What causes my such a reaction?" and puts the answer to the Bug Report title.

пʼятниця, 15 липня 2016 р.

Agility of "agile"

As for me, currently a "new renaissance" of Agile (with capital "A") followers is going on. With their not getting the spirit of agile manifesto, but just following "best" practices and rules from some guide books, not regarding the reality, context and consequences of their deeds. (It may be connected to the new generation of IT employees stepping on the scene.)

That's why it's great that there appear new posts on this subject, trying to educate people about the difference between "agile" and "Agile".
Here is a post I liked recently from Yegor Bugayenko: 12 Mistakes in Agile Manifesto.


понеділок, 23 травня 2016 р.

"Done" for everyone!

Probably each of us had that dialogue with a developer:
- How is your task? Is it okay?
- Yeah! It's done!
- Where can I test it?
- No, it's not yet covered with unit tests / not passed code review / the last commit is almost there.


(Google points here for this picture: https://hoangluongsjsu.wordpress.com/ )

What is missing here is not exactly "Definition of "Done"", but a substitution of different levels of "Done":
- Personal "Done": "I can do nothing more about it", the task is handed over to another team member."
- Team's "Done": "We have done all we could do internally. Now we can demonstrate the results to a wider audience, but we are still open for changes and suggestions in case of interference with some other team."
- Project's "Done": "We ship it! All your claims and change requests you should send to our legal department."

Working with agile Scrum-like process which states team commitment, we should always put the Team's "Done" to tasks' Acceptance Criteria.
Because putting personal commitments to a task description looks like avoiding responsibility for possible future changes in its scope due to integration issues.
But putting project oriented goals is even worse as they are likely not to be testable at the point, when a particular task is done. That leads to "requirements inflation", when the "key project points" are written everywhere and at the same time are not met anywhere.

Watch your requirements. And keep your task descriptions clear and testable.

пʼятниця, 22 квітня 2016 р.

Agile and numbers



In his recent post, Seth Godin writes:
When you measure the wrong thing, you get the wrong thing. Perhaps you can be precise in your measurement, but precision is not significance.
On the other hand, when you are able to expose your work and your process to the right thing, to the metric that actually matters, good things happen.
We need to spend more time figuring out what to keep track of, and less time actually obsessing over the numbers that we are already measuring.



This is the essential part of the "agile development".
In my current team we spend lots of time on "Backlog grooming sessions" arguing on numbers, getting asked "why is it 5 not 8?"
On the same time, nobody cares on getting the Burndown Chart to look like burn down. The reason is "We have many important and urgent tasks with vague deadlines emerging meanwhile in the sprint."
So on our "Sprint planning" meeting we are basically putting the "precisely measured" tickets to a heap of immeasurable ones. What we get is precisely immeasurable. Like dropping 10 carat diamonds to a bucket of soil and trying to estimate the bucket weight.
What precision we might get?


Moreover, the measurement does not influence our actions in any way.
Our the most precise scale of estimations probably should have 3 values:
- "It's OK to try to do this now"
- "Better not to try now"
- "We don't know"
Having the priorities in place, this simple scale will give us enough information to plan sprints, and dramatically reduce time spent on estimation and planning.

середа, 20 квітня 2016 р.

Test Design Strategy

Updated my Test Strategy Template with a new section.
Enjoy :-) Comments are welcome!

Test Design Strategy

Test Design activity is a process of identifying and formalizing Test Cases and Test Suites (in forms of Check Lists, mind maps, etc.) in regards to risk weights, i.e. the value customers might loose if the test is not conducted; or in other words, the risk of unawareness of the unwanted behavior of the system.
Each Test Case is explicitly related to a piece of Requirements, as well as to Test Suites it is run under.

понеділок, 15 лютого 2016 р.

Where to start to automate your checks?


So you are an almost only off-shore tester on a project, and want to automate some of your daily checks to have more time for actual testing. But you lack skills to do it right, or you think you do. And the automation tools and frameworks do not suddenly appear in a project. Somebody needs to implement them.


This picture is familiar to lots of us. But how can we push the deal out of this vicious circle? If not directly to a project's but for self-development sake?

We often hear the management saying: “We do not need automation at this point.”
And they are right!
They do not need an automation of those checks YOU PROPOSED, if it is done by YOU INSTEAD of the work you are hired for, especially in that weedy way YOU NOW would do it.
Whole disadvantage from their perspective!


Starting to write code is always hard and slow at the beginning, because the code quality is in direct proportion to an amount of hours one spent attentively staring at it. So here I propose the first points to look at start:

вівторок, 15 вересня 2015 р.

Testing Strategy Template

This is a list of ideas to consider when reviewing the software development process at your project. It gives you a base-line to compare to what you already have, and simplified understanding of what you may improve.

Стратегія Тестування.
Як на мене, подібні списки ідей потрібні, щоб посидіти й поміркувати, чи все у вас на проекті так добре працює, як хотілося б, і одразу побачити шляхи покращення у кожній фазі процесу розробки.

Testing Strategy Template



Purpose


Testing is a continuous and integrated process where all parties in the project are involved. The purpose of this Test Strategy is to create a shared understanding of the overall targets, approach, tools and timing of (not only) test activities. The objective is to achieve higher quality and shorter customer request lead times with minimum overhead, frequent deliveries, close teamwork with team and the customer, continuous integration, short feedback loops and ability of frequent changes of the design. Test strategy guides us through the common obstacles with a clear view of how to evaluate the system. Lets us look at the development process as a whole.