Testing:Process: Difference between revisions
From Hackepedia
Jump to navigationJump to search
No edit summary |
m typo fixes |
||
| (One intermediate revision by one other user not shown) | |||
| 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]] turned on, 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 7: | Line 7: | ||
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 | Once you're done, turn your logging back to a regular level (turn off debug mode) and continue to watch and make sure that everything seems to be running as expected. | ||
Latest revision as of 17:06, 28 March 2006
Make sure you have verbose logging turned on, 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 debug mode) and continue to watch and make sure that everything seems to be running as expected.
