super_si

.

[Edited by super_si - 6/3/2003 2:34:35 PM]

super_si

I know all testing etc did it last 2 years

got the email cheers.

Just writing it all up


cool sites
Si

[Edited by super_si - 6/3/2003 7:36:25 PM]

super_si

Yet again lectures give us some crap to do no-ones heard of

Basically its a test plan, so what do i include

Value used, Validation, Expect output.

How do i write it, report form or Excel sheet?

Also need some Requirements too, Functional and Non functional requirements??

Cheers

Si

MartinM

Me again Random thoughts....

Requirements come first :
Functional - direct behaviour of the system:
- take two numbers, multiply them and print the answer
- report an error if either number is negative
Non-functional
- must respond within 5 milliseconds
- must use a Windows GUI

Testing
Black box/white box? (go look in Google)
Test plan:
- to test the requirements are met
- tests traceable back to requirements

Functional tests test functional requirements
Non-functional tests test non-functional requirements

Use Excel as a documentation tool to define the test objectives, log test outcomes, re-tests etc

Use a test form for each test:
- pre-conditions
- test data
- expected results
- actual results
- test result (pass/fail)
- re-test results

Functional tests normally exercise valid expected vales, extreme but valid values, invalid values etc

There are different levels of test: unit/integration/system/acceptance

...etc etc

HTH, Martin

DemonDave

iTrader: (13)

http://www.cs.utexas.edu/users/s2s/l...b/doc/VVP.html

super_si

Cheers martin, just being reading my Ian Sommerville, White box black box

Someones said my DFD is impossible to make, any thoughts.

Cheers once again

Si

MartinM

Well, to be pedantic (I am, as you know), you don't 'make a DFD' anyway - you generally make a computer application that has user-oriented or batch functions that allow business processes to be performed in an automated fashion. The DFD just defines the data flows and datastores that you need to take into consideration. Heavy eh?

Being more practical, you obviously don't make a DFD 'cos it doesn't define the windows, fields, validation, detailed processing rules, error messages etc etc that make up a complete application specification (ie the functional and non-functional requirements, as we talked about above)

From what I remember from your DFD it looked reasonably OK - I think there might have been some analysis errors still in there, but it's not possible to uncover them without more detailed discussion - well, more detailed than you can get on a BB by us typing at each other anyway! Maybe that's why someone said you couldn't 'make' your DFD???

Martin

super_si

Cheers martin, im just writing my plan up, anychance i could email it across?

Cheers

Si

MartinM

Well, just this once but I won't make a habit of it

You've got 15 minutes to spot this email address, then it's going to be edited out...<<gone>>

Don't send anything over 200K - ZIP if need be.

I'll try and look at it sometime before 9am tomorrow

[Edited by MartinM - 6/4/2003 11:07:29 PM]

Scooby Dooby Blue

In our final exams last week, we were asked to outline black and white box testing.
A classmate knew what the whitebox was (top down etc) but couldn't remember anything about black box testing so opted for the comedy approach...
'A strategy to assess whether or not a bottle blonde highlights her pubes'

I'm sure that'll go down a treat with the external verifiers

super_si

Lost email address

Done all the work

Si