testssl.sh/t
Dirk Wetter c643860701 Modernize 08_isHTML_valid.t
and make it similar to 07_isJSON_valid.t or 20_baseline_ipv4_http.t
in terms of output and readability
2019-11-16 12:41:44 +01:00
..
01_ca_hashes_up_to_date.t Rename file according to new scheme 2019-05-05 13:44:02 +02:00
07_isJSON_valid.t remove -p from json unit test 2019-08-12 12:38:47 +02:00
08_isHTML_valid.t Modernize 08_isHTML_valid.t 2019-11-16 12:41:44 +01:00
09_isJSON_severitylevel_valid.t renamed 2019-05-05 13:42:48 +02:00
20_baseline_ipv4_http.t Update to newest template 2019-05-06 11:20:28 +02:00
21_baseline_ipv6_http.t.DISABLED Update to newest template 2019-05-06 11:20:28 +02:00
23_client_simulation.t Update to newest template 2019-05-06 11:20:28 +02:00
25_baseline_starttls.t swap ldap server as previous one wasn't reachable anymore 2019-09-25 09:36:16 +02:00
51_badssl.com.t Rename file according to new scheme 2019-05-05 13:44:02 +02:00
59_hpkp.t.tmpDISABLED Rename file according to new scheme 2019-05-05 13:44:02 +02:00
Readme.md Better phrased and provide examples 2019-05-06 11:13:37 +02:00

Naming scheme

  • 00-09: Does the reporting work at all?
  • 20-39: Do scans work fine (client side)?
  • 50-69: Are the results what I expect (server side)?

Please help to write Travis/CI tests! Documentation can be found here. You can consult the existing code here. Feel free to use 20_baseline_ipv4_http.t or 23_client_simulation.t as a template.