MedVision ad

Help - Project - Test data and deskchecks (2 Viewers)

atschamp

New Member
Joined
Mar 17, 2004
Messages
15
Location
Grafton NSW
Gender
Undisclosed
HSC
N/A
Hi im currently doing my major software assignment which is due monday 26th and im kinda stuck and cant ask my teacher for help because its like spose to be fully completed and just into the finalising stage lol.. anyways...
my problem:

there are 2 types of test data/deskchecking in my assignment.. first at algorithm stage and then at black box stage... i have already completed the algorithm stage in the first phase of my assignment. in the alg stage i did simple test data that tested boundaries (as i made a maths prog) like simply when calculating the range test data to check for a negative range or input of text then created the deskcheck which involved putting the test data in showing the display and then a column to say if it was ok or not.....

my problem is how do i do the black box stage? as far as i can see from my text book its the same as the alg stage except the user dosent know hte expected outputs so do i use the same test data ... how does this work ...? what columns (headings) do i need in my deskcheck? please help
 

jm1234567890

Premium Member
Joined
Aug 18, 2002
Messages
6,516
Location
Stanford, CA
Gender
Male
HSC
2003
I balck box testing you would test the features of your program and if expected output was generated.
 

SamD

Member
Joined
Jul 21, 2002
Messages
256
Gender
Male
HSC
N/A
You're now doing system level testing, so you're testing all aspects of your program whilst it is actually running, a deskcheck is not relevant/possible at this level of testing, rather just report the results. Perhaps a passed/failed column and then a column describing what happened when it failed. Some possible test scenarios include:
-confirm processing is correct using normal data (use your algortihm test data and check the real system produces the expected results).
-try all sorts of weird inputs (such as entering text where numeric values are expected, click on buttons in strange sequences, exit at odd times, etc...)
-test execution on different operating systems and hardware.
-get some inexperienced and experienced users to run the software and record any problems or issues.
-if applicable/possible, try entering heaps of data (volume testing)
-try running your program whilst running heaps of other big programs (a type of load testing)
-check it installs on a variety of different systems (if its windows, does it install in Win 95, 98, 2000, Me, and XP?)

HTH
Sam
 

Users Who Are Viewing This Thread (Users: 0, Guests: 2)

Top