Jira (PDOC-88) Create a plan for ensuring strings support going forward
Title: Message Title Henrik Lindberg commented on PDOC-88 Re: Create a plan for ensuring strings support going forward We may need a test matrix of puppet versions as well. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-88) Create a plan for ensuring strings support going forward
Title: Message Title William Hopper commented on PDOC-88 Re: Create a plan for ensuring strings support going forward Todo: investigate what we have setup for strings in CI right now. We'd like to run the latest version of strings against a small fixture suite (acceptance). A 'don't break strings' acceptance test in puppet may be the way to do this. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-88) Create a plan for ensuring strings support going forward
Title: Message Title Hailee Kenney created an issue Puppet Strings / PDOC-88 Create a plan for ensuring strings support going forward Issue Type: Task Assignee: Unassigned Created: 2016/07/07 8:51 AM Priority: Normal Reporter: Hailee Kenney If the docs team is going to rely on strings, we need to make sure that new releases of puppet do not break it in such a way that it becomes unusable. That means that new releases of puppet cannot cause strings to have any of the following issues: Fail to finish running Emit corrupted JSON or other bad things Any of the requirements defined by the PDOC-59 epic are no longer met (e.g. failing to pick up function definitions, etc) Testing for strings is incredibly minimal right now. At the very least, we need to improve unit tests and add unit tests for JSON output. We probably also need to add some actual acceptance testing. It may be that better testing is all that's needed here, but before the docs team can integrate strings we have to be able to assure that it's maintained properly along with new releases of puppet.
