Boost Testing :
From: Robert Ramey (ramey_at_[hidden])
Date: 2007-11-29 11:35:49
I always liked the compiler_status approach.
I altered it to suit my needs and called it library status. Its in the
A sample of its output can be found at:
> What is the correct way to generate local html files for analyzing
> your tests? It looks like report.py is the correct script to use, but
> I'm not sure what syntax to use when calling it. Ideally, I would like
> to call it immediately after run.py
> In the past I was only running process_jam_log and compiler_status,
> now that I'm running the sanctioned way with run.py, running
> compiler_status no longer seems to work.