From: John Wiegley <jwiegley@gmail.com>
To: Oliver Charles <oliver.g.charles@googlemail.com>
Cc: emacs-orgmode Org-Mode <emacs-orgmode@gnu.org>
Subject: Re: Personal unit testing within org mode?
Date: Fri, 23 Oct 2009 06:37:38 -0400 [thread overview]
Message-ID: <3B8782C2-6F7C-4FA3-AE6F-1AA45781B005@gmail.com> (raw)
In-Reply-To: <5641883d0910230308i41ff7d01g5b448018732e991c@mail.gmail.com>
On Oct 23, 2009, at 6:08 AM, Oliver Charles wrote:
> I think tests can be defined as a new keyword sequence: (sequence
> "TEST" "|" "PASSED" "FAILED"). All unit tests are set to repeat daily,
> and have state change logging enabled. So when you move from TEST ->
> PASSED, it logs this and then moves back to TEST. SImple so far right?
>
> Well another important part is being able to review how well I've done
> in the last week, and this is where org-habit comes in. I'm thinking
> of ripping off that little graph it produces, but the problem I have
> is where should I put it? Do you think it will work in the agenda, or
> should I generate some type of custom view? Perhaps something like
> generating time clock reports?
Doesn't org-habit, with repeating tasks, already give you just what
you've described above? All you need to do is add the todo states to
your #+TODO line at the top of your Org file. Then they will repeat
as you've described, and reporter progress below. You'd have to
simulate FAILED condition by just not recording the task as done, and
a PASSED if you do achieve it. Then the habits graph could be
meaningful for this.
John
prev parent reply other threads:[~2009-10-23 10:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 10:08 Personal unit testing within org mode? Oliver Charles
2009-10-23 10:37 ` John Wiegley [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3B8782C2-6F7C-4FA3-AE6F-1AA45781B005@gmail.com \
--to=jwiegley@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=oliver.g.charles@googlemail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).