forked from irccom/devdocs
-
Notifications
You must be signed in to change notification settings - Fork 2
/
tools.html
28 lines (26 loc) · 1.7 KB
/
tools.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
---
title: Testing Tools
layout: short-header
ntitle: Tools
nsub: Resources and tools we use to test IRC software
---
<div class="row">
<div class="col-sm-3 col-xs-12 sidebar">
<div class="docs-list-sidebar">
<div class="docs-list-sidebar">
<!-- <h4><a href="#foundation">Foundation Tools</a></h4>
<h4><a href="#external">External Tools</a></h4> -->
</div>
</div>
</div>
<div class="col-sm-9 col-xs-12 main-content">
<div class="docs-list-content content">
<h3><a href="https://hub.docker.com/u/irccom">IRC Server Docker Test Images</a></h3>
<p>We host a series of Docker images <a href="https://hub.docker.com/u/irccom">available here</a> (source <a href="https://github.com/irccom/test-servers">here</a>) with different IRC server software running. These images are setup with consistent configurations, oper credentials, and port numbers to speed-up testing.</p>
<h3><a href="https://github.com/irccom/script-runner">Test Script Runner</a></h3>
<p>We've written an IRC script runner <a href="https://github.com/irccom/script-runner">available here</a> which makes it simple to run a set of commands and actions across different IRC servers, then output a file for easy comparison between the tested servers.</p>
<h3><a href="https://github.com/ircdocs/parser-tests">Parser Tests</a></h3>
<p>The set of test files <a href="https://github.com/ircdocs/parser-tests">available here</a> let developers test IRC parsers and uncover areas where they do not parse (particularly complicated or edge-case) messages or incoming lines correctly.</p>
</div>
</div>
</div>