The learned lesson

I am testing different web application for a long time but started testing flex application for few months and it is so interesting. But the main blocker is the poor knowledge of advance new flex application and the back end technology that used for application that i am testing. So there is lot of opportunity to overlooked something and when i am onto something fishy i missed the over all big picture. 

Most of the time i am testing with Firefox because that support the flex debugger so that if any exception occurs i can trace it out. And thats the major mistake i have made that i make myself comfortable on Firefox and make it as a habit of my testing. 

I have to say each and every testers should use the IE as a default browser and first they have to know the customer configuration which IE there use mostly. I think preferable is IE 6 And 7 that is most of the people now a days use. 

Here is the browser Stats below:

Browser Statistics Month by Month

2010	IE8	IE7	IE6	Firefox	Chrome	Safari	Opera
May	16.0%	9.1%	7.1%	46.9%	14.5%	3.5%	2.2%
April	16.2%	9.3%	7.9%	46.4%	13.6%	3.7%	2.2%
March	15.3%	10.7%	8.9%	46.2%	12.3%	3.7%	2.2%
February	14.7%	11.0%	9.6%	46.5%	11.6%	3.8%	2.1%
January	14.3%	11.7%	10.2%	46.3%	10.8%	3.7%	2.2%
2009	IE8	IE7	IE6	Firefox	Chrome	Safari	Opera
December	13.5%	12.8%	10.9%	46.4%	9.8%	3.6%	2.3%
November	13.3%	13.3%	11.1%	47.0%	8.5%	3.8%	2.3%
October	12.8%	14.1%	10.6%	47.5%	8.0%	3.8%	2.3%
September	12.2%	15.3%	12.1%	46.6%	7.1%	3.6%	2.2%
August	10.6%	15.1%	13.6%	47.4%	7.0%	3.3%	2.1%
July	9.1%	15.9%	14.4%	47.9%	6.5%	3.3%	2.1%
June	7.1%	18.7%	14.9%	47.3%	6.0%	3.1%	2.1%
May	5.2%	21.3%	14.5%	47.7%	5.5%	3.0%	2.2%
April	3.5%	23.2%	15.4%	47.1%	4.9%	3.0%	2.2%
March	1.4%	24.9%	17.0%	46.5%	4.2%	3.1%	2.3%
February	0.8%	25.4%	17.4%	46.4%	4.0%	3.0%	2.2%
January	0.6%	25.7%	18.5%	45.5%	3.9%	3.0%	2.3%

Stat taken from: http://www.w3schools.com/browsers/browsers_stats.asp

I will discuses about the production deployment process soon. Keep in touch and enjoy your testing.

Scrum and our testing

I was thinking for a long time to start my writing again on my blog and for this bought my own domain for it. Here it goes for today's topic.


Agile and Testing


I have gone through some blogs on how we can improve testing in agile specially in scrum, also how we testers can be more involved in each stories in sprints. In scrum we use "Team" for everything and i think that help us all to focus and not to point anyone for any problem. So as a "Team" we always discuss for better ways to improve our productivity. And i was trying to improve our testing ways. 


For our perspective what we do?

1. After our planing meeting, I start preparing test cases for our stories and we share those test cases in wiki so that it will be easily accessible for product owners and for team. And test team can engage with better understanding for all stories.
2. We select one test scenario (That scenario should cover most of the paths for that story) for our cucumber feature file (automation) 
3. We write that selected test case as a cucumber feature file format so that we can just copy paste that feature file from wiki. 
4. If we found any scenario that is not clear, we discuss that with product owner. (This is the main reason why we want to do test case in the beginning of the sprint so that we can find out the scenarios as much as possible and it help us when doing the regression test)
5. As we go on with our standup each day, we keep updating test cases if changes or if we discover any new scenarios.
6. Before one day of the sprint we freeze our code (we don't develop features but we fix our bugs)
7. Last day of our sprint is for regression of cucumber automation scripts, unit test and manual regression of all the stories done by this sprint. 
8. We are ready for the sprint review next day. 
9. We use teamcity (build and release management) application runs all our scripts each day and notify us by mail (passed or failed). 

I have read some blog about the documentation in scrum and i think if anything makes your product better and suites you then you can take those. 


In agile "Team" is responsible for anything that goes wrong. so when we are going regression in production after any new deployment, our whole team involves in regression testing and we have a to do list in front of us for manual testing some of the major part of our application. 


I think test cases for each story, focused on cucumber automation script & also unit test for each story can make you feel better or to ensure you that those parts passed before is not broken by new builds.

You can also look into my presentation slides for agile testing on the side bar >>>>