Luca Salvarani

> Did this feature regress somehow? I'm very confused when trying to write my spec: > > This test: `The file '/tmp/repo/dummy.ts' should exist` > > Fails: > > ```...

I finally figured it out... This feature **did not regress**. It just **never came out as a release**. 😀 The PR #233 introducing the `should exist` syntax was merged in...

Do you have Chrome installed? > selenium.common.exceptions.WebDriverException: Message: unknown error: cannot find Chrome binary (Driver info: chromedriver=2.39.562718 (9a2698cba08cf5a471a29d30c8b3e12becabb0e9),platform=Windows NT 10.0.18363 x86_64)

Yet another **workaround** inspired by @apowers313 approach: ```python # -------------- src/package/config/schemas.py -------------- import dataclasses from pathlib import Path from dynaconf import Dynaconf @dataclasses.dataclass class SettingsSchema(Dynaconf): myProperty: str myCategory: "CategorySettingsSchema" @dataclasses.dataclass...

> Great idea / example @LukeSavefrogs :) > > Note that you can change [line 75](https://gist.github.com/apowers313/c009991a31195e9e3ee8dc51b989136a#file-dynaconf_plus_pydantic-py-L75) of my example from `extra="forbid"` to `extra="allow"` and get pretty much the same thing...

Strange... Seems like testing the output instead works as expected: ``` #shellcheck shell=sh Describe "Demo" trailing_empty_line() { printf "1\n2\n\n" } It "Last empty line is not counted" When call trailing_empty_line...

@shinokada The problem in your code is in this lines: ``` The output should eq "apples oranges pears grapes" ``` ## Why #### Expected output You're telling `shellspec` to check...

Wow! Very useful! I added this workflow to a project of mine already using `shellspec` and now it's great seeing that tests are run every time a pull request is...

This would be a very useful addition since tests could easily **hang**.. As of now (version `0.28.1`) i had to use the **timeout command** myself inside the tests (not portable):...

I currently have the same issue - Are you running `shellspec` using **Cygwin** on **Windows**? - Do you see **this line** (near the end) when running it? ``` [...] Finished...