comments

szabgab · Nov 7, 2024 · bb25ba5 · bb25ba5
1 parent f4256d2
commit bb25ba5
Show file tree

Hide file tree

Showing 4 changed files with 22 additions and 4 deletions.
diff --git a/sites/en/pages/subtest.txt b/sites/en/pages/subtest.txt
@@ -5,7 +5,7 @@
 =status show
 =books testing
 =author szabgab
-=comments_disqus_enable 1
+=comments_disqus_enable 0
 
 =abstract start
 

diff --git a/sites/en/pages/test-for-expected-warnings.txt b/sites/en/pages/test-for-expected-warnings.txt
@@ -6,7 +6,7 @@
 =books testing
 =author szabgab
 =archive 1
-=comments_disqus_enable 1
+=comments_disqus_enable 0
 
 =abstract start
 

diff --git a/sites/en/pages/testing-for-no-warnings.txt b/sites/en/pages/testing-for-no-warnings.txt
@@ -4,7 +4,7 @@
 =status show
 =author szabgab
 =archive 1
-=comments_disqus_enable 1
+=comments_disqus_enable 0
 
 =abstract start
 
@@ -213,3 +213,7 @@ Result: FAIL
 Feel free to use either of these solutions. I personally still prefer the use of plans, but the <hl>done_testing</hl>
 also has its place and the <hl>Warn::FailWarnings</hl> module has nicer reports.
 
+<h2>Comments</h2>
+
+Another advanced warning usage is custom categories definition. Then you could enable a fine-grained exception system based on your requirements and make warn statements FATAL in your test suites.
+https://perldoc.perl.org/warnings#Reporting-Warnings-from-a-Module
diff --git a/sites/en/pages/virtualenv-in-perl.txt b/sites/en/pages/virtualenv-in-perl.txt
@@ -4,7 +4,7 @@
 =status show
 =author szabgab
 =archive 1
-=comments_disqus_enable 1
+=comments_disqus_enable 0
 
 =abstract start
 
@@ -68,3 +68,17 @@ export PATH=venv/bin/:$PATH
 </code>
 
 
+<h2>Comments</h2>
+
+Also check out carton... A much more robust way of doing this.
+
+<hr>
+
+Does not work: I exactly followed your instructions.
+
+$ cpanm -l venv/ --installdeps .
+--> Working on .
+Configuring /Users/tperiasa/work/perl-dev ... OK
+find_module_by_name() requires a package name at /usr/local/bin/cpanm line 35.
+
+