bleah, internet access on trains suxxors... and Im heading down to Karlskrona for Mon-Wed!!
Monday, 30. June 2008, 07:12:02
unbelievable.. how can SwedishRails even call this internet access.. and then also charge like... 120SEK(10€) for 2-3h of access.. =/
Anyway, im heading down to our second(or first) office which is based on Karlkrona in Blekinge(iirc) in the southern part of sweden. Im gonna meet up with the devs there and talk about how we can include QA mentality into there work and how we can make user that Im able to test things that are made down there, especially considering that Im based in another office 500KM away from them... I think it will work out fine, but we just have to agree on where to start work on this and what kind of expectations we should have considering all the different aspects of remote QA of applications and trying to get QA in the mindset of the devs.
Ofc, you might think that im just completely diss'ng the devs now, saying that I have to show them the QA mindset bla bla bla. Im NOT doing that.. however, sometime the devs dont see the other side of the coin when it comes to testing and it's different aspects. When testing something 'ad-hoc'(re-active testing, ie search for bug/find bug/report bug) you can pretty much take any software and just try to break it. That is fine and does not essentially requrie any greater plan or specifications. However, if you plan on doing a 'pro-active' testrun, this is a different story. When running a pro-active testrun you need access to how an application/feature/button/GUI should work according to the specification on that application/feature/button/GUI. Then, based on the testcases which you build up from the specification, you can start to test and report 'pass/fail' states... and here is the part where some devs miss out and dont see the point of having a specification set and written down for a feature/element inside a application. Ofc, this is easily fixed by mentioning this to the devs and asking them for a specification on each feature/element which you need to test....
...Ok.. not sure why I wrote all this text here.. but.. anyway.. this is a blogg and you are supposed to write down you thoughts in a blogg.. yes?
CyA!
Anyway, im heading down to our second(or first) office which is based on Karlkrona in Blekinge(iirc) in the southern part of sweden. Im gonna meet up with the devs there and talk about how we can include QA mentality into there work and how we can make user that Im able to test things that are made down there, especially considering that Im based in another office 500KM away from them... I think it will work out fine, but we just have to agree on where to start work on this and what kind of expectations we should have considering all the different aspects of remote QA of applications and trying to get QA in the mindset of the devs.
Ofc, you might think that im just completely diss'ng the devs now, saying that I have to show them the QA mindset bla bla bla. Im NOT doing that.. however, sometime the devs dont see the other side of the coin when it comes to testing and it's different aspects. When testing something 'ad-hoc'(re-active testing, ie search for bug/find bug/report bug) you can pretty much take any software and just try to break it. That is fine and does not essentially requrie any greater plan or specifications. However, if you plan on doing a 'pro-active' testrun, this is a different story. When running a pro-active testrun you need access to how an application/feature/button/GUI should work according to the specification on that application/feature/button/GUI. Then, based on the testcases which you build up from the specification, you can start to test and report 'pass/fail' states... and here is the part where some devs miss out and dont see the point of having a specification set and written down for a feature/element inside a application. Ofc, this is easily fixed by mentioning this to the devs and asking them for a specification on each feature/element which you need to test....
...Ok.. not sure why I wrote all this text here.. but.. anyway.. this is a blogg and you are supposed to write down you thoughts in a blogg.. yes?
CyA!
WIDGETIZE