| // Protocol Buffers - Google's data interchange format |
| // Copyright 2008 Google Inc. All rights reserved. |
| // https://developers.google.com/protocol-buffers/ |
| // |
| // Redistribution and use in source and binary forms, with or without |
| // modification, are permitted provided that the following conditions are |
| // met: |
| // |
| // * Redistributions of source code must retain the above copyright |
| // notice, this list of conditions and the following disclaimer. |
| // * Redistributions in binary form must reproduce the above |
| // copyright notice, this list of conditions and the following disclaimer |
| // in the documentation and/or other materials provided with the |
| // distribution. |
| // * Neither the name of Google Inc. nor the names of its |
| // contributors may be used to endorse or promote products derived from |
| // this software without specific prior written permission. |
| // |
| // THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS |
| // "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT |
| // LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR |
| // A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT |
| // OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, |
| // SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT |
| // LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, |
| // DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY |
| // THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT |
| // (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE |
| // OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. |
| |
| // Author: kenton@google.com (Kenton Varda) |
| |
| #include <google/protobuf/compiler/java/java_doc_comment.h> |
| |
| #include <gtest/gtest.h> |
| |
| namespace google { |
| namespace protobuf { |
| namespace compiler { |
| namespace java { |
| namespace { |
| |
| TEST(JavaDocCommentTest, Escaping) { |
| EXPECT_EQ("foo /* bar */ baz", EscapeJavadoc("foo /* bar */ baz")); |
| EXPECT_EQ("foo /*/ baz", EscapeJavadoc("foo /*/ baz")); |
| EXPECT_EQ("{@foo}", EscapeJavadoc("{@foo}")); |
| EXPECT_EQ("<i>&</i>", EscapeJavadoc("<i>&</i>")); |
| EXPECT_EQ("foo\u1234bar", EscapeJavadoc("foo\\u1234bar")); |
| EXPECT_EQ("@deprecated", EscapeJavadoc("@deprecated")); |
| } |
| |
| // TODO(kenton): It's hard to write a robust test of the doc comments -- we |
| // can only really compare the output against a golden value, which is a |
| // fairly tedious and fragile testing strategy. If we want to go that route, |
| // it probably makes sense to bite the bullet and write a test that compares |
| // the whole generated output for unittest.proto against a golden value, with |
| // a very simple script that can be run to regenerate it with the latest code. |
| // This would mean that updates to the golden file would have to be included |
| // in any change to the code generator, which would actually be fairly useful |
| // as it allows the reviewer to see clearly how the generated code is |
| // changing. |
| |
| } // namespace |
| } // namespace java |
| } // namespace compiler |
| } // namespace protobuf |
| } // namespace google |