\ No newline at end of file
diff --git a/test/functional/test_site/expected/requirements/SpecifyingRequirements._include_.html b/test/functional/test_site/expected/requirements/SpecifyingRequirements._include_.html
index f09190e433..352bb5ca51 100644
--- a/test/functional/test_site/expected/requirements/SpecifyingRequirements._include_.html
+++ b/test/functional/test_site/expected/requirements/SpecifyingRequirements._include_.html
@@ -1,13 +1,13 @@
-
Specifying requirements
+
Specifying requirements
As we establish requirements, they should be recorded in some way for future reference, usually called a requirement specification. Furthermore, it is advisable to show these requirements to stakeholders, and refine requirements based on their feedback.
The next phase is to convert requirements into a product specification that specifies how the product will address the requirements.
Given next are some tools and techniques that can be used to specify requirements. Note that they can also be used for establishing requirements too.
-
Textual descriptions (unstructured prose)
+
Textual descriptions (unstructured prose)
This is the most straight forward way of describing requirements. A textual description can be used to give a quick overview of the domain/system that is understandable to both the users and the development team. Textual descriptions are especially useful
when describing the vision of a product. However, lengthy textual descriptions are hard to follow.
-
Feature list
+
Feature list
It is a list of features (or functionalities) grouped according to some criteria such as priority (e.g. must-have, nice-to-have, etc. ), order of delivery, object or process related (e.g. order-related, invoice-related, etc.). Here is a sample feature
list from Minesweeper (only a brief description has been provided to save space).
Path within the boilerplate folder is separately specified
+
Path within the boilerplate folder is separately specified
This is dynamically included.
Like static include, pages within the site should be able to use files located in folders within boilerplate.
Also, the boilerplate file name (e.g. inside.md) and the file that it is supposed to act as (notInside.md) can be different.
diff --git a/test/functional/test_site/expected/siteData.json b/test/functional/test_site/expected/siteData.json
index 8fca18165f..0ddd90eca0 100644
--- a/test/functional/test_site/expected/siteData.json
+++ b/test/functional/test_site/expected/siteData.json
@@ -266,6 +266,15 @@
"globalAndFrontMatterOverrideProperty": "Overridden by global override",
"headings": {},
"headingKeywords": {}
+ },
+ {
+ "src": "testIncludePluginsRendered.md",
+ "title": "Included files should have plugins rendered on them",
+ "layout": "default",
+ "globalOverrideProperty": "Overridden by global override",
+ "globalAndFrontMatterOverrideProperty": "Overridden by global override",
+ "headings": {},
+ "headingKeywords": {}
}
]
}
diff --git a/test/functional/test_site/expected/sub_site/index._include_.html b/test/functional/test_site/expected/sub_site/index._include_.html
index 4f089ec675..da17da8813 100644
--- a/test/functional/test_site/expected/sub_site/index._include_.html
+++ b/test/functional/test_site/expected/sub_site/index._include_.html
@@ -1,5 +1,5 @@
This is a page from another Markbind site.
-
Feature list
+
Feature list
It is a list of features (or functionalities) grouped according to some criteria such as priority (e.g. must-have, nice-to-have, etc. ), order of delivery, object or process related (e.g. order-related, invoice-related, etc.). Here is a sample feature
list from Minesweeper (only a brief description has been provided to save space).
Trying to access an imported variable via namespace:
+
Trying to access an imported variable via namespace:
There should be something blue below:
This is a deeply imported variable
Something should have appeared above in blue.
\ No newline at end of file
diff --git a/test/functional/test_site/expected/testIncludePluginsRendered.html b/test/functional/test_site/expected/testIncludePluginsRendered.html
new file mode 100644
index 0000000000..75e52afa3e
--- /dev/null
+++ b/test/functional/test_site/expected/testIncludePluginsRendered.html
@@ -0,0 +1,73 @@
+
+
+
+
+
+
+
+
+
+ Included files should have plugins rendered on them
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
The contents of these two panels should be exactly the same.
+
+
+
+
+ header Content of panel
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/test/functional/test_site/expected/testPanels/NestedPanel._include_.html b/test/functional/test_site/expected/testPanels/NestedPanel._include_.html
index a4b5b4139a..abd9590c4c 100644
--- a/test/functional/test_site/expected/testPanels/NestedPanel._include_.html
+++ b/test/functional/test_site/expected/testPanels/NestedPanel._include_.html
@@ -1 +1 @@
-
Nested Panel
\ No newline at end of file
+
Nested Panel
\ No newline at end of file
diff --git a/test/functional/test_site/expected/testPanels/NormalPanelContent._include_.html b/test/functional/test_site/expected/testPanels/NormalPanelContent._include_.html
index 4da1693276..a82ad044a5 100644
--- a/test/functional/test_site/expected/testPanels/NormalPanelContent._include_.html
+++ b/test/functional/test_site/expected/testPanels/NormalPanelContent._include_.html
@@ -1 +1 @@
-
Normal panel content heading
\ No newline at end of file
+
Normal panel content heading
\ No newline at end of file
diff --git a/test/functional/test_site/expected/testPanels/PanelNormalSource._include_.html b/test/functional/test_site/expected/testPanels/PanelNormalSource._include_.html
index fcce7c140a..e80b7a53c8 100644
--- a/test/functional/test_site/expected/testPanels/PanelNormalSource._include_.html
+++ b/test/functional/test_site/expected/testPanels/PanelNormalSource._include_.html
@@ -1 +1 @@
-
Panel normal source content headings
\ No newline at end of file
+
Panel normal source content headings
\ No newline at end of file
diff --git a/test/functional/test_site/expected/testPanels/PanelSourceContainsSegment._include_.html b/test/functional/test_site/expected/testPanels/PanelSourceContainsSegment._include_.html
index ebc62d08a9..3f76bbdf60 100644
--- a/test/functional/test_site/expected/testPanels/PanelSourceContainsSegment._include_.html
+++ b/test/functional/test_site/expected/testPanels/PanelSourceContainsSegment._include_.html
@@ -1,4 +1,4 @@
-
Panel source segment content headings
+
Panel source segment content headings
-
This heading is not src of any panel, so it should not be in the search data
\ No newline at end of file
+
This heading is not src of any panel, so it should not be in the search data
\ No newline at end of file
diff --git a/test/functional/test_site/expected/testPanels/boilerTestPanel._include_.html b/test/functional/test_site/expected/testPanels/boilerTestPanel._include_.html
index 34701a2b3b..cd49919927 100644
--- a/test/functional/test_site/expected/testPanels/boilerTestPanel._include_.html
+++ b/test/functional/test_site/expected/testPanels/boilerTestPanel._include_.html
@@ -1 +1 @@
-
boilerplate test for panel heading
\ No newline at end of file
+
boilerplate test for panel heading
\ No newline at end of file
diff --git a/test/functional/test_site/expected/testPanels/notInside._include_.html b/test/functional/test_site/expected/testPanels/notInside._include_.html
index 6756ecc64d..bacd089bd9 100644
--- a/test/functional/test_site/expected/testPanels/notInside._include_.html
+++ b/test/functional/test_site/expected/testPanels/notInside._include_.html
@@ -1 +1 @@
-
heading in panel boilerplate
\ No newline at end of file
+
heading in panel boilerplate
\ No newline at end of file
diff --git a/test/functional/test_site/needsrenderedplugin.md b/test/functional/test_site/needsrenderedplugin.md
new file mode 100644
index 0000000000..c59ef97855
--- /dev/null
+++ b/test/functional/test_site/needsrenderedplugin.md
@@ -0,0 +1 @@
+header Content of panel
\ No newline at end of file
diff --git a/test/functional/test_site/site.json b/test/functional/test_site/site.json
index 88be588979..aa9d603ee7 100644
--- a/test/functional/test_site/site.json
+++ b/test/functional/test_site/site.json
@@ -75,6 +75,10 @@
{
"src": "testCodeBlocks.md",
"title": "Code Blocks Line Splitting"
+ },
+ {
+ "src": "testIncludePluginsRendered.md",
+ "title": "Included files should have plugins rendered on them"
}
],
"ignore": [
diff --git a/test/functional/test_site/testIncludePluginsRendered.md b/test/functional/test_site/testIncludePluginsRendered.md
new file mode 100644
index 0000000000..5f99d413ba
--- /dev/null
+++ b/test/functional/test_site/testIncludePluginsRendered.md
@@ -0,0 +1,7 @@
+The contents of these two panels should be exactly the same.
+
+
+
+
+header Content of panel
+
\ No newline at end of file