Add tests for snippet files; #13

Author: Marek Suchánek

data/generated/minimal-snippet.adoc

@@ -0,0 +1,4 @@
+.Minimal snippet
+
+
+

data/generated/snip_some-notes-in-a-snippet-file.adoc

@@ -0,0 +1,42 @@
+////
+Base the file name on the snippet title. For example:
+* file name: snip-my-snippet-a.adoc
+* Title: .My snippet A
+
+A snippet is not a module. Consider storing snippet files in a separate snippets folder.
+
+Indicate the content type in one of the following ways:
+Add the prefix snip- or snip_ to the file name.
+Add the following attribute before the title:
+:_content-type: SNIPPET
+////
+
+.Some notes in a snippet file
+////
+The title is optional in a snippet. Use the block title syntax, such as .My snippet A, rather than a numbered heading, such as = My snippet A.
+
+In the title of snippets, include nouns or noun phrases that are used in the body text. This helps readers and search engines find the information quickly. Do not start the title of snippets with a verb. See also _Wording of headings_ in _The IBM Style Guide_.
+
+Do not specify an ID for the snippet title.
+////
+
+A text snippet is a small fragment of text that is stored in an AsciiDoc file. Text snippets contain content that is reused in multiple modules or assemblies, for example:
+
+* A step or series of steps in a procedure
+* A disclaimer, for example, for technology preview or beta releases
+
+[NOTE]
+--
+Additional guidance or advice that improves product configuration, performance, or supportability.
+--
+
+[IMPORTANT]
+--
+Advisory information essential to the completion of a task. Users must not disregard this information.
+--
+
+[WARNING]
+--
+Information about potential system damage, data loss, or a support-related issue if the user disregards this admonition. Explain the problem, cause, and offer a solution that works. If available, offer information to avoid the problem in the future or state where to find more information.
+--
+

src/main.rs

@@ -83,7 +83,6 @@ fn main() -> Result<()> {
     // * It must be generated after the other modules so that it can use their include statements
     if let Some(title) = cmdline_args.value_of("include-in") {
         // Gather all include statements for the other modules
-        // TODO: Figure out if this can be done without calling .to_owned on all the Strings
         let include_statements: Vec<String> = non_populated
             .into_iter()
             .map(|module| module.include_statement)
@@ -205,6 +204,20 @@ mod tests {
         assert_eq!(reference.text, pre_generated);
     }
 
+    /// Test that we generate the snippet file that we expect.
+    #[test]
+    fn test_snippet_file() {
+        let mod_type = ModuleType::Snippet;
+        let mod_title = "Some notes in a snippet file";
+        let options = basic_options();
+        let snippet = Module::new(mod_type, mod_title, &options);
+
+        let pre_generated =
+            include_str!("../data/generated/snip_some-notes-in-a-snippet-file.adoc");
+
+        assert_eq!(snippet.text, pre_generated);
+    }
+
     // These values strip down the modules to the bare minimum.
     fn minimal_options() -> Options {
         Options {
@@ -267,4 +280,17 @@ mod tests {
 
         assert_eq!(reference.text, pre_generated);
     }
+
+    /// Test that we generate the snippet file that we expect.
+    #[test]
+    fn test_minimal_snippet() {
+        let mod_type = ModuleType::Snippet;
+        let mod_title = "Minimal snippet";
+        let options = minimal_options();
+        let snippet = Module::new(mod_type, mod_title, &options);
+
+        let pre_generated = include_str!("../data/generated/minimal-snippet.adoc");
+
+        assert_eq!(snippet.text, pre_generated);
+    }
 }