QA Bean

It is all began long time ago when Development Teams were constantly asked to provide estimate and they were having a hard time to properly face the task. Let's admit it, there are so many things that can change, happen, and simply go wrong during the development process that one can hardly expect a proper estimation of hours for each task. That why a relative estimation with Story Points came along. Story Points Estimation Its a different way to estimate the effort of the Scrum Development Team with-in Agile methodology, which means that instead of estimating hours of work the team estimates each effort relatively to other efforts in the project. Let's assume that a developer knows that specific 'Task 1' is much harder than another 'Task 2' it is hard for him/her to quantify that harder feeling in hours of additional work but it is possible to say that it much more work. This situation is being address by Story Points when each story point is ...

For those of you who start with HP ALM, or using it for basic functionality and looking to increase the capacity of the tool, I wanted to mention one of the most powerful features within HP ALM, and the one that sets it above the competitors - the ability to fully customize most of sections within the tool. This customization goes as far as giving the possibility to create new buttons with customizable functionality, updating functionality of existing functions and adding fields to different components. All that can be achieved through HP ALM’s workflow section. This sections allows configuration of day to day functionality like preventing defect from being closed without a reason, to a more complex customization with have VBScripting like exports, execution or even initiation of other tools and applications. In future posts I’m planning to explore some specific application of this powerful tool, meanwhile for those who interested here are some examples of what can be achieved...

I have noticed in many places that are working on implementing Agile methodology a popular misconception around the question who are the Scrum Development Team. Most people wrongly assume that it is the de facto developers who write the code and when I point out that it is not the case it is being met by dismay and skepticism. "Developers are developers, who else can development team be?" I was told once in a such discussion, and the answers to that is hidden with in the Scrum guide If one will go and carefully review the guide one can find the following definition there: "The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of "Done" product at the end of each Sprint." Take a note of the phrase "... rofessionals who do the work of delivering..." those are not only the developers who write the code but also the Testers who test the code, the BAs who taking care of Backlog items ...

Lately, I found myself helping several people to begin their automation testing journey. And what a better place to do it then a nice new installation of a Robot Framework with its Selenium2Library on a Windows OS. Why Robot Framework with Selenium2Library? While you are probably here because you are looking for a quick installation guide for Automation Testing platform for you web project, I still need to do my do diligence and explain in couple of words why we need it. Robot Framework it's a Python framework that allows for a less development oriented Manual QA professionals to do a quick switch into Test Automation. This can be achieved by allowing for easy English phrases (e.g. Click Element, Wait, etc) to replace a more complex Python syntax. Selenium2Library it's additional add on on top of Robot Framework that allows easy interaction with web elements during the automation process. That's it..... DONE with the talking now the installation.... Installatio...