1
I Use This!
Inactive
Analyzed about 19 hours ago. based on code collected 1 day ago.

Project Summary

Ever heard of test driven development? What about test driven administration? Take a look around examples/ folder for example tests that you can run agains your server.

The general configuration should be done through the test-server.yaml and should be managable by any non Perl awear admin (are there any?). Of course you are free to put any other test that make sence for your server.

The idea behind this is following: You run prove /etc/t and everything is fine. Server is up and running. Life is nice. Then somebody calls you at 3am... Oups! What went wrong? You login to the server (if possible of course) and run the prove /etc/t friend. Something failed? => fix it. Nothing failed? => write a test that will reveal that something is wrong && fix the problem of course ;). And then at 6am go happily to sleep again...

To be the administration really test drive ;) you should be writing your tests before you install the server...

Any other benefits? What about migration || reinstalation of the server? Do you always remember what services || purpouses is the server used for? You just scp the /etc/t folder to the new machine and prove /etc/t will tell you. If not you'll write a test ;).

Or are you writing firewall rules and need to check if you didn't close some ports that you should not? Check out the 03_open-ports.t.

Tags

administration linux server testing

In a Nutshell, Test::Server...

Artistic License 2.0
Permitted

Commercial Use

Modify

Distribute

Sub-License

Private Use

Forbidden

Hold Liable

Use Trademarks

Required

Include Copyright

State Changes

Include Install Instructions

Rename

These details are provided for information only. No information here is legal advice and should not be used as such.

GNU General Public License v2.0 or later
Permitted

Commercial Use

Modify

Distribute

Place Warranty

Forbidden

Sub-License

Hold Liable

Required

Distribute Original

Disclose Source

Include Copyright

State Changes

Include License

These details are provided for information only. No information here is legal advice and should not be used as such.

This Project has No vulnerabilities Reported Against it

Did You Know...

  • ...
    nearly 1 in 3 companies have no process for identifying, tracking, or remediating known open source vulnerabilities
  • ...
    anyone with an Open Hub account can update a project's tags
  • ...
    in 2016, 47% of companies did not have formal process in place to track OS code
  • ...
    compare projects before you chose one to use

30 Day Summary

Mar 19 2024 — Apr 18 2024

12 Month Summary

Apr 18 2023 — Apr 18 2024

Ratings

1 user rates this project:
4.0
   
4.0/5.0
Click to add your rating
  
Review this Project!