Difference between revisions of "Testing:Process"

From Hackepedia
Jump to navigationJump to search
 
Line 1: Line 1:
# Make sure you have verbose logging, usually called "debug mode" when doing any type of testing. Make sure you are watching the logs in real time.
+
Make sure you have verbose [[logging]], usually called "debug mode" when doing any type of testing. Make sure you are watching the logs in real time.
  
 
  tail -f /var/log/messages
 
  tail -f /var/log/messages
Line 5: Line 5:
 
is a common example to have running in an unused [[terminal]].
 
is a common example to have running in an unused [[terminal]].
  
# Try examples that should return both positive and negative results and see how it affects the logs. Try as many different approaches as possible with your examples, so you catch any potential errors.
+
Try examples that should return both positive and negative results and see how it affects the logs. Try as many different approaches as possible with your examples, so you catch any potential errors.
  
 
Once you're done, turn your logging back to a regular level (turn off debud mode) and continue to watch and make sure  and everything seems to be running as expected.
 
Once you're done, turn your logging back to a regular level (turn off debud mode) and continue to watch and make sure  and everything seems to be running as expected.

Revision as of 12:51, 25 October 2005

Make sure you have verbose logging, usually called "debug mode" when doing any type of testing. Make sure you are watching the logs in real time.

tail -f /var/log/messages

is a common example to have running in an unused terminal.

Try examples that should return both positive and negative results and see how it affects the logs. Try as many different approaches as possible with your examples, so you catch any potential errors.

Once you're done, turn your logging back to a regular level (turn off debud mode) and continue to watch and make sure and everything seems to be running as expected.