Hello All,
The next LTG is on the 15th July 2010 and will be at:
The Shooting Star.
125-129 Middlesex Street
http://tinyurl.com/29t87r2
Closest tube is Liverpool St
The plan: We have the function room from 5pm onwards.
The Software Testing Club and Stuart Taylor/Trader Media Grp are chipping in and part sponsoring the evening.
http://events.linkedin.com/London-Tester-Gathering-15th-July/pub/349816
Hope to see you there.
Cheers and Kind Regards
Tony Bruce.
Tuesday, 15 June 2010
Friday, 4 June 2010
Username is already exists!
I got an email from the Agile Journal about Agile Connect 2010. Online Agile conference. Cool! Talk to people around the world online. Cool!
So I signed up. Or tried to.
I received a rather curt 'Please enter a valid email' message after filling out the registration and using my pretty standard Googlemail address.
OK maybe not so curt because it does have 'please' in the message but the word 'address' would have been good too. Somehow missing the 'address' makes it seem curt to me.
Do they not like Google or have they got some weird validation rules going on?
I got to the next sign up bit and had to stick in address details and stuff. As it's none of their business and an online conference I went with my standard '1 Na Street'. I found it interesting when I had to pick a profession. I couldn't see Dev or Test or BA or PM or anything along those lines. I could see 'People with the money'. Although it's apparently not just a trade show.
I got curious and decided to spend a couple of minutes snooping.
First, the great messages you get if you try sign up with the same details.
I checked Fiddler and there were a couple of things that popped out at me but the biggest would be my registration details......ALL OF MY REGISTRATION DETAILS. My password helpfully listed twice.
You may think 'So what? Kind of the point of Fiddler isn't it?' and I would say 'Yes, yes it is but usually you would have to decrypt the traffic first, cause you know, security and all that.'
Not so for the Agile Journal! Security?! Encryption?! HTTPS?! What?
Anyway, lunch break over, back to work but if you decide to attend Agile Connect 2010 I'd suggest using a password that you don't use for anything else.
So I signed up. Or tried to.
I received a rather curt 'Please enter a valid email' message after filling out the registration and using my pretty standard Googlemail address.
OK maybe not so curt because it does have 'please' in the message but the word 'address' would have been good too. Somehow missing the 'address' makes it seem curt to me.
Do they not like Google or have they got some weird validation rules going on?
I got to the next sign up bit and had to stick in address details and stuff. As it's none of their business and an online conference I went with my standard '1 Na Street'. I found it interesting when I had to pick a profession. I couldn't see Dev or Test or BA or PM or anything along those lines. I could see 'People with the money'. Although it's apparently not just a trade show.
I got curious and decided to spend a couple of minutes snooping.
First, the great messages you get if you try sign up with the same details.
I checked Fiddler and there were a couple of things that popped out at me but the biggest would be my registration details......ALL OF MY REGISTRATION DETAILS. My password helpfully listed twice.
You may think 'So what? Kind of the point of Fiddler isn't it?' and I would say 'Yes, yes it is but usually you would have to decrypt the traffic first, cause you know, security and all that.'
Not so for the Agile Journal! Security?! Encryption?! HTTPS?! What?
Anyway, lunch break over, back to work but if you decide to attend Agile Connect 2010 I'd suggest using a password that you don't use for anything else.
Tuesday, 1 June 2010
Spitballing at RapidFTR
A couple of weeks ago I was lucky enough to be able to attend another RapidFTR CodeJam generously hosted by USwitch. More on USwitch here.
A bit of time was spent getting environments ready and we were off. We split into teams and I joined the Blackberry group. We started with getting a semi layout/semi infracstructure drawing up on the board so we all knew what we were dealing with.
And the Devs left to do Devy things and I stayed with the board to think testing things, which meant, questions, lots of questions.
I ended up with this.
I started with thinking about what I was looking at and then thinking about what I would want to test and what information I needed and what information I thought was lacking as a whole.
Here's a couple of post notes close up. Probably be a bit hard to read as my writing is atrocious.
I must admit, I've been lazy though and haven't put these up on the wiki yet or asked the questions of anybody. I will make sure I do that this week.
It did lead to the team asking what models of Blackberry we should be concerned about which is a good start.
I can see from the Google group that the stories are progressing, story progress is being tracked on Mingle, defects are as well.
Code is on Github as is the wiki.
So I made a small stack of sticky notes with a lot of questions, questions I haven't asked yet but will do.
A bit of time was spent getting environments ready and we were off. We split into teams and I joined the Blackberry group. We started with getting a semi layout/semi infracstructure drawing up on the board so we all knew what we were dealing with.
And the Devs left to do Devy things and I stayed with the board to think testing things, which meant, questions, lots of questions.
I ended up with this.
I started with thinking about what I was looking at and then thinking about what I would want to test and what information I needed and what information I thought was lacking as a whole.
Here's a couple of post notes close up. Probably be a bit hard to read as my writing is atrocious.
I must admit, I've been lazy though and haven't put these up on the wiki yet or asked the questions of anybody. I will make sure I do that this week.
It did lead to the team asking what models of Blackberry we should be concerned about which is a good start.
I can see from the Google group that the stories are progressing, story progress is being tracked on Mingle, defects are as well.
Code is on Github as is the wiki.
So I made a small stack of sticky notes with a lot of questions, questions I haven't asked yet but will do.
I then moved onto a bit of ET, looking at the search function, have a few more ideas there, not quite finished. I want to know if I can manipulate the data during transfer, essentially muck about with the posts and gets. I'm going to try this week.
And that was the day pretty much gone! Don't know where it went cause it went quick, maybe I was slacking.
The project could do with a few more testers. I was kinda surprised I was the only one. It might be because these Devs do a lot of acceptance testing but testers will still be needed so sign up!
And that was the day pretty much gone! Don't know where it went cause it went quick, maybe I was slacking.
The project could do with a few more testers. I was kinda surprised I was the only one. It might be because these Devs do a lot of acceptance testing but testers will still be needed so sign up!
It could also do with people who have experience with Blackberrys, developing and testing.
If you can help, get in touch.
If you can help, get in touch.
Subscribe to:
Posts (Atom)