Weekend Testing

I went online at around 1130PM Saturday hunting for some challenge to exercise my sleepless mind. Pinged Ajay and Manoj on GTalk and they had plans of testing a product. After around 45 min spent on researching what to test we finally decided upon www.tinyurl.com

The mission was simple hunt for bugs, and so did we. The session was fantastic; bugs started flowing from the first minute, and all three of us had loads of fun. The test techniques varied individually and the discussions we had during the test session been great.

Once we were thru with the session, Manoj and me left and Ajay did almost most of the post production. So, it would be nice to read the full report from his blog @ http://enjoytesting.blogspot.com/2009/08/trio-testing-at-distance-part-1.html

So, next time if you are not feeling sleepy or feel like practicing your test skills with other testers or feel like learning some thing new or feel like sharing your test ideas, or just curious to know what this is all about. Drop a mail to weekendtesting@gmail.com

Thanks Manoj and Ajay for helping me sleep. (This statement is a bit controversial :)

Read On:

Bangalore Weekend Testers: Fun, Learn & Contribute - Pradeep Soundararajan
BWT - Do you wanna Rock? - Parimala Shankaraiah
Are you Ready? Join : Bangalore Weekend Testers - Ajay Balamurugadas
Here comes BWT – Learn, Test and have Fun - M.V.Manoj

Comments

Skeeve said…
Hi

After dropping a mail we ended up chatting and whilest getting to know eachother ended up testing each others company web page. And getting kind of competitive.

Found errors:
B&O website:
*)Searcing for " " really did search for all space's in website.
( And multiple whitespaces were not treated as one).
*)an SQL error was shown to user when an object was not found
correctly.
*) String "false" was shown on image gallery for some reason.

EFI website:
*) Search function ignored whitespaces but still showed them
in search box
*) Required email field did not check for "@" character.
*) When Returning customers email was asked characters "a" and "@" were accepted as correct. But "asdfasdf" was not.
*) incorrect address on addressbar gave standard web explorer 404 error. It was not handled by web server

Might have been more, but it was fun.
August 13, 2009 at 4:32 PM
Ajay Balamurugadas said…
Hi Skeeve,

It was me who chatted with you.

And the unofficial healthy competition was between us. :)

Regards,
Ajay
August 20, 2009 at 12:57 AM
Post a Comment

Popular posts from this blog

Exploratory testing, Session based testing, Scripted testing…concertedly

In my last assignment a mix of exploratory, session based and scripted testing helped won an award, appreciation by managers & stake holders at our organization. The quotes from our award certificate “ QA team has come up with some intelligent testing techniques to validate the product. The customer test team was not able to find even a single critical bug after delivery ” Though the award was a small one in terms of the award categories our organization have, it meant a lot to me and the team, because this was the first time the team used exploratory approach. The assignment was not pure exploratory or session based, in fact it was supposed to be scripted, but a mix of all three exploratory, session based and scripted testing helped us learn, enjoy, and meet our mission. The assignment started off with developing test cases. We wrote test cases based on the initial requirement document provided. We did come up with a large number of test cases, of which most were re-written, some
Read more

What do you do when you find a bug?

What do you do when you find a bug? Hold on do not answer it right now. Let me first set the context. You are part of an agile team. The developers sit opposite to you. You are testing a feature in a session. You are time bound and have the good habit of capturing notes when you test. When you now find a bug what do you do? Assuming that you have taken enough notes you go on to write a good bug description and may capture a screen shot, video of the bug and continue with your session. At the end of the session do you Open the defect tracking tool (wait for it to load), enter all the fields for a bug, upload necessary evidence and have the tool share the defects with your dev team? Or Open the defect tracking tool (wait for it to load), enter all fields for a bug, upload necessary evidence and then compose an email to the dev team with the bug id’s/descriptions? Or Walk to the developer share your notes; reproduce it if required, work together to identify the problem? I work in
Read more

Regression Checks + Regression testing = Regression testing?!

One of the questions I find hard to answer when I use exploratory test techniques in my project is,”How do you run regression tests? How do you prioritise them? Do you automate them? Do you document regression test cases?” And then a bunch of questions follow. Let me define the context. I work closely with developers; we use either Scrum or Kanban - which ever best suits our project, product owner, business. We do not believe in individual metrics, blame games, stringent processes, and heavy documentation. All we care about is to deliver high quality software. This does not mean that there is no process, metrics or documentation. We have them all, but they are there to meet our needs and to help those who will come onboard to support/maintain the software. Regression Checks At the start of a story, testers pair up with developers to develop feature files using SpecFlow. Some call it Acceptance Test Driven Development and others Behaviour Driven Development [I am yet to figure out the d
Read more