Specs (tests) not listed, are there limits over name of spec markdown files?

[rfennell]

I have a query over adding TestSpace to a new repo, the tests are now shown

Setup

I have tried to setup Testspaces on a new repo i.e. one that only contained a readme.md and license.

I added the /.testspace.yml containing

manual:

In the /specs folder, I added the most basic spec I could in the file test a.md

---
testspace:
---

# Q1

## Q1a

What I see

There are no tests show in the TestSpaces UI

But the file is in the repo

The strange this is that, if I add a new file /specs/ABC.md and copy in the content from `/specs/test a.md', the copy shows up in the UI.

Questions

This has left me confused, so a couple of questions

• Are the limitation over the names of the spec files?
• Is there a way to see a log that shows the spec file discovery process (as to why a file is not found)?

I am sure it is something I have done wrong, over filename or markdown format

[munderseth]

Hi @rfennell I see the specs. Are still not seeing them?

[rfennell]

Thanks for pointer, it is looking a really interesting tool

[rfennell]

So you recommend using Jekyll as a preview to make sure the markdown is OK? I had just been using the preview in VSCode.

[munderseth]

If you start leveraging variables and includes /w parameters the Spec Preview becomes very helpful when designing tests. Also when writing lots of tests, it can be helpful reviewing them dynamically using a second tab.

[munderseth]

Can you try the following (if you have time 😄 ):

• Go to https://github.com/testspace-com/hello.manual and select Use this template to create a repo
• Then under your new repo - Code - select Codespaces (a very nice new feature by GitHub)
• The following the readme instructions - https://github.com/testspace-com/hello.manual#spec-preview

[rfennell]

That worked perfectly to allow previewing.

And yes, Codespaces are great, perfect for this type of thing. I have been using them all day for my explorations