• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Rob Spoor
  • Tim Cooke
  • Junilu Lacar
Sheriffs:
  • Henry Wong
  • Liutauras Vilda
  • Jeanne Boyarsky
Saloon Keepers:
  • Jesse Silverman
  • Tim Holloway
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
Bartenders:
  • Al Hobbs
  • Mikalai Zaikin
  • Piet Souris

NX: how to test the completed assignment

 
Ranch Hand
Posts: 102
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
I am worrying about how to test the assignment to meet the Sun spec.
Could somebody give me any suggestion?
Best regards!
Frank
 
author and jackaroo
Posts: 12199
280
Mac IntelliJ IDE Firefox Browser Oracle C++ Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Frank,
For the GUI: give it to a dumb end user and ask them what they think. Seriously. There are so many times that we as programmers think we have got a good interface going, but end users hate it because it doesnt do what they think it should to get a desired job done.
For the database, there have been many posts regarding how to test it (try searching "test locking" and / or "test database"). One example is this thread which even gives some example code for a test application (for FBNS). The testing strategy usually boils down to setting up multiple threads to attempt to do a certain amount of changes. Ensuring that record locking / blocking works, and that dead locks were removed (not strictly a requiremnt).
For the airline task we were decrementing number of seats available, so many people tested by doing something like setting up 100 threads to book 1 seat from a flight that only had 95 seats available. Eventually 5 of them should report that they failed to get the seat, and the database should show 0 seats remaining.
Everywhwere in your specifications that there is a "MUST" statement, think about how you can test that it does work, and more importantly think about what could be done to try and break it - then write some code to try all the scenarios you thought about.
If possible, test on different PCs, and hopefully across a network. Set your server on one machine, and your client on another - does it work?
Does your GUI still look OK on another operating system? In theory this shouldnt matter, as it appears that the examiners will try and test using the same environment you built on (same OS release and same JDK). However if your GUI does not look OK under another OS, then you may have missed something when you designed the app, and if the examiner notices what you missed, then you could loose points.
Regards, Andrew
 
frank sun
Ranch Hand
Posts: 102
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,Andrew
Thanks a lot for your suggestion, I would try according to you, and I think I will post some others questions about it when doing it.
Regards!
Frank
 
reply
    Bookmark Topic Watch Topic
  • New Topic