Files
carbon-lang/proposals/scripts/proposals_test.py
T
Jon Meow 1e8930e21b Bazelify the jekyll handling. (#230)
- Shift some things around to adjust to being in bazel.
- Add separate build/serve/publish scripts for use by bazel (not set up for direct execution, but bazel requires +x).
- Fix some tests I noticed not running unittest.main as a result of the switch.
- Move md files into filegroups for build reuse.
- Disable automatic site publishing (now `bazel run //website/jekyll:publish`)

Site publishing seems like it'd be too much trouble to keep automated... The C++ toolchain essentially needs to be set up due to the repo config, along with syncing the LLVM submodules, etc. That seems a bit annoying to do on each run of the publish-docs action, and not something I really want to maintain. If we get a CI, we can focus on it more there, but this feels like it'd just be a one-off to maintain as a github workflow.
2020-12-29 15:15:24 -08:00

30 lines
774 B
Python

"""Tests for proposals.py."""
__copyright__ = """
Part of the Carbon Language project, under the Apache License v2.0 with LLVM
Exceptions. See /LICENSE for license information.
SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
"""
import unittest
from carbon.proposals.scripts import proposals
class TestProposal(unittest.TestCase):
def test_get_path(self):
proposals_path = proposals.get_path()
p = proposals.get_list(proposals_path)
self.assertEqual(
p[0],
(
"0029 - Linear, rebase, and pull-request GitHub workflow",
"p0029.md",
),
)
self.assertEqual(p[1], ("0029 - Decision", "p0029_decision.md"))
if __name__ == "__main__":
unittest.main()