markdown VS spectest

I previously introduced the nao1215/markdown package as a markdown builder for the Go language (previously it was go-spectest/markdown, but the Owner has changed). What syntax do you want when writing markdown? I thought it was important to support mermaid. When we write design documents, we should be able to write not only text but also sequence diagrams and ER diagrams.

The spectest dynamically generates markdown without using text/template, however instead utilizes its own Markdown Builder (go-spectest/markdown) during the markdown generation.

I previously introduced a feature in the go-spectest/spectest, which extracts error messages from Golang unit test results.

The go-spectest/spectest project provides commands and libraries related to testing. While the library is specialized for API testing, the commands are designed to be usable by all Golang users (meaning you don't need to use the spectest library).

However, implementing end-to-end (E2E) tests can be quite labor-intensive. To achieve a return on the effort invested, I am developing go-spectest/spectest.

Currently, I am developing an E2E testing framework called go-spectest/spectest. Spectest is a package forked from steinfletcher/apitest, and I have been gradually adding its unique features. To enhance spectest further, I believe it's best to actually test APIs.