Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make tests more predictable by publishing default content stubs #182

Closed
caendesilva opened this issue Apr 28, 2022 · 2 comments
Closed

Make tests more predictable by publishing default content stubs #182

caendesilva opened this issue Apr 28, 2022 · 2 comments

Comments

@caendesilva
Copy link
Member

caendesilva commented Apr 28, 2022

Adding a todo:

To make testing more predictable, I want to create stubs for the content files that should be included in Hyde installs.
These would be:

  • _pages\index.blade.php
  • _pages\404.blade.php
  • _site\media\app.css

Before and after each test all content directories are deleted, and createsdefaultdirectories are run, and stubs republished.

The backup file helpers can then also be removed, as tests should never be run in a production environment.
Edit: Keeping the file helpers as I'm keeping the backup/restores of other files that are not in the scope of content files, such as config files etc.

Originally posted by @caendesilva in #181 (comment)

caendesilva added a commit to hydephp/hyde that referenced this issue Apr 28, 2022
@caendesilva
Copy link
Member Author

The contents of this issue has been implemented, however they add several seconds to the test time.

@caendesilva
Copy link
Member Author

Fixed it so it is actually faster than before.

caendesilva added a commit to hydephp/develop that referenced this issue Jun 7, 2022
caendesilva pushed a commit that referenced this issue Jul 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant