Calling all testers !!

[original PM]

yeah I got that - which was worrying - I think I will have a quick chat with the landlord later today

[Sysman]

aaaah you are into your real ale then..

you should get down to my local - The Local

Note the beer is much better than the website....

Big fail on that website. I got a warning message "Do you want Safari to accept an incoming network connection?". No thanks.

[mudskipper]

What they all said

But don't forget to give a bit of thought to other 'pre release' or what some people call pre-production testing. This would usually be non functional, e.g. performance, backout, failover, d.r. etc. If it's a web app, is it introducing new servers or being served by existing ? Can you project the size of the user base ? Is the user base constant or will it be introduced to more users over time ? Better test for it now.

Yes - and things like compliance testing if you're doing credit card stuff and pen testing (specialist companies who do that stuff for you) if it's a website.

[mudskipper]

aaaah you are into your real ale then..

you should get down to my local - The Local

Note the beer is much better than the website....

Think we cycled past it on our Lejog ride last year!

[original PM]

aaaah you are into your real ale then..

you should get down to my local - The Local

Note the beer is much better than the website....

[mudskipper]

I believe it involves pint glasses and little paper umbrellas...

http://www.loddonbrewery.com/show_picture-d-1-1115.html

Not normally presented with umbrella, but perhaps I'll ask for one next time.

[TestMangler]

What they all said

But don't forget to give a bit of thought to other 'pre release' or what some people call pre-production testing. This would usually be non functional, e.g. performance, backout, failover, d.r. etc. If it's a web app, is it introducing new servers or being served by existing ? Can you project the size of the user base ? Is the user base constant or will it be introduced to more users over time ? Better test for it now.

[cojak]

thanks k2p2 and eek most useful!

k2p2 I will get you a hullabaloo - if I knew what one was!

I believe it involves pint glasses and little paper umbrellas...

[original PM]

thanks k2p2 and eek most useful!

k2p2 I will get you a hullabaloo - if I knew what one was!

[eek]

Oooh, oooh, I know this one (having winged the tester foundation certification just last week!)

Testing types -

I guess you're talking about black box (functional testing), white box (code analysis), and experience based testing. For the first two, there are standard techniques for deriving suitable test cases - things like boundary analysis (10 or fewer widgets, postage £2, > 10, free postage), branch coverage (white box) etc. Experience based testing is to try and pick up the stuff that the test cases won't cover - and is generally undertaken by an experienced tester or developer who knows how to break stuff - the kind of person who'll enter javascript into your username field (and is available from 20th July!)
Also think about static testing - e.g. running a webpage through a compliance checker as well as automated testing - more useful for regression tests.


Test stages

Unit testing, component testing, integration testing, system testing, User Acceptance testing regression testing, maintenance testing. You may combine system and integration testing as they're often co-dependent. These broadly relate to project phases - i.e. UAT = business requirements, ST = functional specs, Unit testing = coding - ideally you'd design the tests at the right time in the project, but, even if you haven't it's useful to think of them in those terms.


Amount of time it should take - not sure on this one - guess it depends how good the code is and how experienced the testers are. Metrics from previous projects can be used. Ideally you start early - a review of requirements is 'testing'.

Pitfalls - not taking it seriously / putting up experienced resources / thinking that once no defects are found, none exist. Seeing testers as obstructive. Lack of communication, prioritisation, usual management failings!

Witty anecdotes - there are none. Testing is horrible.

Mine's a hullabaloo.

On the time front (theory suggests) the earlier in the development cycle you start testing the less testing you require. Personal experience says different but that's life. Supposedly testing should be 50% of the total development time but its a very hard sell to most clients.


Pitfalls include all the above plus the customer believing bug fixes are free because the system has been tested.

Witty anecdotes. Its testing usual done by people for whom software development is too exciting.

[mudskipper]

Hi All (Specifically Mich and Mangler) but also anyone who has some experiecne of testing

I have been asked to write a piece on testing for our internal project web resource and whilst I have some knowledge it is always a good idea to get the experts point of view.

So to that end any info you can supply on

Testing Types,
Test Phases,
Amount of time testing should take (when compared to lenght of dev time)
Common Pitfalls of testing
Whitty Anecdotes!

Anything else which may be useful.

Sorry cannot pay in cash but will by beer if the chance arises!

TIA

Oooh, oooh, I know this one (having winged the tester foundation certification just last week!)

Testing types -

I guess you're talking about black box (functional testing), white box (code analysis), and experience based testing. For the first two, there are standard techniques for deriving suitable test cases - things like boundary analysis (10 or fewer widgets, postage £2, > 10, free postage), branch coverage (white box) etc. Experience based testing is to try and pick up the stuff that the test cases won't cover - and is generally undertaken by an experienced tester or developer who knows how to break stuff - the kind of person who'll enter javascript into your username field (and is available from 20th July!)
Also think about static testing - e.g. running a webpage through a compliance checker as well as automated testing - more useful for regression tests.


Test stages

Unit testing, component testing, integration testing, system testing, User Acceptance testing regression testing, maintenance testing. You may combine system and integration testing as they're often co-dependent. These broadly relate to project phases - i.e. UAT = business requirements, ST = functional specs, Unit testing = coding - ideally you'd design the tests at the right time in the project, but, even if you haven't it's useful to think of them in those terms.


Amount of time it should take - not sure on this one - guess it depends how good the code is and how experienced the testers are. Metrics from previous projects can be used. Ideally you start early - a review of requirements is 'testing'.

Pitfalls - not taking it seriously / putting up experienced resources / thinking that once no defects are found, none exist. Seeing testers as obstructive. Lack of communication, prioritisation, usual management failings!

Witty anecdotes - there are none. Testing is horrible.

Mine's a hullabaloo.

[original PM]

Hi All (Specifically Mich and Mangler) but also anyone who has some experiecne of testing

I have been asked to write a piece on testing for our internal project web resource and whilst I have some knowledge it is always a good idea to get the experts point of view.

So to that end any info you can supply on

Testing Types,
Test Phases,
Amount of time testing should take (when compared to lenght of dev time)
Common Pitfalls of testing
Whitty Anecdotes!

Anything else which may be useful.

Sorry cannot pay in cash but will by beer if the chance arises!

TIA