As a software tester, I hope you already know the value of focussing on a specific task. There has been many studies to prove that multi-tasking is not as effective as we may think and cost of switching context in our brain is huge. That is why practices such as session based testing are so effective.
However, it's easier said than done. Distractions are everywhere. You can be distracted easily by
- A Twitter or Skype notification on your computer screen.
- A noisy workplace environment.
- Your manager or a colleague.
- A call or a text message on your cell phone.
- Push notification from apps like Facebook, What's App, Linked-In, Emails etc.
- Thousands of other things such as smell of food / coffee from the kitchen :-)
It's hard to maintain focus. Do you agree?
We can not remove all the distractions. We can not control all of them. However, some ...
Exciting times :-)
Some of you know that I have been working on Planned Departure for a while now. Till now I was working on it on the part-time basis. However, now we have our team in place and we are moving in our own office. YAY!! My primary focus now would be to drive business and manage development of Planned Departure. If you do not know what Planned Departure is, please have a look at this one minute video.
It's a big problem. Last year, identity of around 2.5 million deceased users was stolen in US alone. Do you want to take the risk or protect your digital assets?
Yesterday I was thinking about the importance of having a pause button for the tester and wrote a post on the Linked-In. In my opinion, without understanding mission and identifying stakeholder, there is no point in focussing on scope and strategy. I have shared my experience to substantiate this claim where asking WHY made a difference in the project I was working on. Please read Remember Why before What and How on Linked-in and let me know your thoughts.
BTW, if you are on Linked-In - feel free to connect with me.
I am sure you have seen this debate many times online. You may also have strong views on whether testers should be able to code or not.
Well, In my opinion - testers should be able to write code.
I have just published my views on this here .
Please have a look - would be nice to hear your views on this.
It was good to meet all the regulars (you know who you are :-)) and many new people. It’s always nice to hear experiences of fellow testers. Incidentally, John from Sauce Labs was also there. Sauce Labs is a special company for our community because of Jason and so it was nice to hear from John how Sauce Labs is progressing.
We invited Costin to share his experience. It was great to get insight on the challenges of testing analytics in mobile world. Unfortunately this talk was not recorded - I will check with him and see if his slide-deck is available somewhere.
One of the main reason for me to go to meet-ups is to learn something new and Costin’s talk gave me plenty of things to learn ...
Selenium Webdriver has become one of the most important tool for testers around the world. Demand for Selenium WebDriver has been increasing over the years and will continue for the foreseeable future. Demand for the Selenium is evident from the increasing number of jobs which require knowledge of Selenium WebDriver (Graph generated from Indeed)
Selenium is an open source project, it has progressed so far because of the monumental efforts of Selenium community. Many people are actively involved in Selenium community and there are many ways to get involved. If you have right skills, you can contribute code, write documentation, help with bugs and so on.
It is also possible to support Selenium community indirectly - by sharing your knowledge, by making it easier for people to use Selenium, by participating in local selenium meet-ups ...
Let’s Test party is over. I am back in London and still trying to absorb everything. I will need to write few blog posts to cover my experience @ Lets Test - this is just start :-)
Let’s Test was on top of my must-attend list from past two years and I am glad I could attend this year. In my opinion, one of the biggest advantage of attending a conferences is being able to confer and Let’s Test provides perfect environment for that.
I reached Stockholm on Sunday and thanks to the power of twitter - I met Richard , Christopher , Geir and Amy at the airport. See the usefulness of this medium? If you are still not on the twitter, come and join us :-)
After checking-in, I headed straight to the lobby and got few tips about the area and nature walk from Carsten . In the next half an hour ...
One of the project I am currently working on had a formal end-to-end testing phase. There are many interrelated systems and end-to-end testing is a good exercise to ensure that system works as expected.
However, it’s important to remember that executing more tests, specially during end-to-end testing phase could be counter productive. In general, I prefer less because constraints make me focus on right and important things.
So for end-to-end testing, let’s assume that product in question is a web-based e-commerce product such as Amazon. A typical end-to-end test for such a product could be on the lines of
- User purchase an item
- An order is generated
- User gets order confirmation
- Inventory is adjusted
- Dispatch system gets order information
- Dispatch is scheduled
- Order status is updated
- User gets notification about dispatch
- Item is dispatched ...