Testing:Process - Revision history

Franks: typo fixes

2006-03-29T01:06:01Z

typo fixes

← Older revision		Revision as of 18:06, 28 March 2006
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 ~~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 debug mode) and continue to watch and make sure that everything seems to be running as expected.

Frankk at 19:51, 25 October 2005

2005-10-25T19:51:43Z

← Older revision		Revision as of 12:51, 25 October 2005
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

Frankk at 19:51, 25 October 2005

2005-10-25T19:51:21Z

← Older revision		Revision as of 12:51, 25 October 2005
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.

Frankk at 19:50, 25 October 2005

2005-10-25T19:50:52Z

New page

# 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.