#48105 create tests - tests subdir - test server/client programs - test scripts
Closed: wontfix None Opened 8 years ago by rmeggins.

The existing code like test-protocol, the test server, etc. should be moved into a tests subdirectory, which should be built by the main build process. See adminutil and admin server for examples of how test programs should be built and run as part of an autoconf project. I don't know if we need a formal test framework yet, but at least a way to run some basic sanity tests of server features.


I found a bug with my previous patch - setting back to review?

commit f16a8fed8e7d09c6ee9846cf4c64ef2571ec3224
Author: Rich Megginson rmeggins@redhat.com
Date: Fri Mar 6 09:37:27 2015 -0700

Metadata Update from @rmeggins:
- Issue assigned to rmeggins
- Issue set to the milestone: 1.3.4 backlog

6 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/1436

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Fixed)

2 years ago

Login to comment on this ticket.