ccm/miti.sh
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Highlight some code-blocks with 'console' label

Browse Source 
Update the dracula theme styles to make 'console' highlighting more legible
This commit is contained in:
Catalin Constantin Mititiuc
2025-06-16 20:18:05 -07:00
parent 791cd692c6
commit 449a41aa85
5 changed files with 36 additions and 31 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
posts/2023-11-15-test-mix-task-file-modify.md
View File

@@ -51,7 +51,7 @@ end
Let's try running the test.
```
```console
$ docker run --rm -w /opt -v $PWD:/opt hw_dev mix test
running build task
...
@@ -197,7 +197,7 @@ File.write("index.html", """
After running the test,
```
```console
$ docker run --rm -w /opt -v $PWD:/opt hw_dev mix test
running build task
...
@@ -207,7 +207,7 @@ Finished in 0.02 seconds (0.02s async, 0.00s sync)
we have our test directory, `test/mix/tmp`,
```
```console
$ find test/mix/tmp
test/mix/tmp
test/mix/tmp/build
@@ -218,7 +218,7 @@ test/mix/tmp/build/index.html
and our fixture file.
```
```console
$ cat test/mix/tmp/build/index.html
<!-- Auto-generated fixture -->
<!DOCTYPE html>
@@ -240,7 +240,7 @@ end)
Now, after we run the tests, all the files and directories created during the test run have been removed.
```
```console
$ find test/mix/tmp/
find: ‘test/mix/tmp/’: No such file or directory
```
@@ -258,7 +258,7 @@ capture_io(fn -> Mix.Tasks.Build.run([]) end)
When we run our tests now, there are no more IO messages cluttering up the test results.
```
```console
$ docker run --rm -w /opt -v $PWD:/opt hw_dev mix test
...
Finished in 0.02 seconds (0.02s async, 0.00s sync)
@@ -319,4 +319,4 @@ end
## Conclusion
This test seemed trivial at first, but increased in complexity quickly. We had to set some of our configuration in application environment variables, change the configuration temporarily before a test run and then change it back after, clean up test artifacts after the run, and capture IO messages that were generated during it. That's enough going on that we thought it would be a good topic for a post. Cheers and happy coding!
This test seemed trivial at first, but increased in complexity quickly. We had to set some of our configuration in application environment variables, change the configuration temporarily before a test run and then change it back after, clean up test artifacts after the run, and capture IO messages that were generated during it. That's enough going on that we thought it would be a good topic for a post. Cheers and happy coding!