Opened 14 years ago
Closed 14 years ago
#418 closed task (fixed)
create an init.sh to share code between tests written sh
| Reported by: | Peter Johansson | Owned by: | Peter Johansson |
|---|---|---|---|
| Priority: | major | Milestone: | svndigest 0.8 |
| Component: | test | Version: | trunk |
| Keywords: | Cc: |
Description
Just like we have the test::Suite class for tests written in C++ it would be handy to have an init.sh that be called in the top of tests in order to init some variable and check VERBOSE env variable or -v switch et cetera.
The good thing is that we can avoid copy&paste, which is fine first time you write the test, but a pain the day you have to fix a bug in that code which pasted in multiple places. Another good thing is that we don't need configure to create every test.sh from a test.sh.in because all variables that are set by configure can be set in init.sh instead and shared between the tests. We only need one CONFIG_FILE that is init.sh.in. This is how it is done in the yat project.
The downside is that the tests will only be callable from one directory, which is $(top_builddir)/test because that is from where Automake calls the tests. How important is it that tests are callable from anywhere?
Btw, this ticket was triggered from when I was working on extending the test of svndigest-copy-cache (#380)
Change History (5)
comment:1 Changed 14 years ago by
| Status: | new → assigned |
|---|
comment:3 Changed 14 years ago by
This involved renaming a couple of foo.sh.in to foo.sh which will cause svn to complain that foo.sh already exists. I could avoid that by renaming to bar.sh instead. Opinions?
comment:4 Changed 14 years ago by
comment:5 Changed 14 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
No feedback, so I suppose it's green light.