From d13a29db9a1f472b732c1c5ce37914f85a95a510 Mon Sep 17 00:00:00 2001 From: Mads Nielsen Date: Tue, 2 May 2017 08:58:10 +0200 Subject: [PATCH] Squashed commit of the following: commit cd87ca708332e8810440535b5d9c07002d7ec20b Author: Mads Nielsen Date: Tue May 2 08:57:48 2017 +0200 Fixed #101. Include test gems in image for now commit 19d2a194549e66bf96ec9c537dd21d2464a69bda Author: Bue Petersen Date: Mon May 1 21:02:46 2017 +0200 Minor note in roadmap (#100) --- Gemfile | 11 ++++------- roadmap.md | 4 ++-- 2 files changed, 6 insertions(+), 9 deletions(-) diff --git a/Gemfile b/Gemfile index 0f1ba55..307191a 100644 --- a/Gemfile +++ b/Gemfile @@ -11,11 +11,8 @@ gem 'flexmock' gem 'zip' gem 'liquid' gem 'xml-simple', '~> 1.1', '>= 1.1.5' - -group :test_gems do - gem 'rspec' - gem 'simplecov' - gem 'simplecov-rcov' - gem 'ci_reporter_test_unit' -end +gem 'simplecov' +gem 'simplecov-rcov' +gem 'ci_reporter_test_unit' +gem 'rspec' diff --git a/roadmap.md b/roadmap.md index b480b7a..41a035c 100644 --- a/roadmap.md +++ b/roadmap.md @@ -8,7 +8,7 @@ The [original blue print](/docs/BluePrint.md) behind a pragmatic automated chang _so we are able to collect information from several systems, one for developers and maybe one with end user docs_. -> In a continuous delivery world we are always ready to release, and as a release also include a changelog, or a release note, and other kind of documentation, these documents must also always be available continuously. .. we recognize that the good release note requires some manual work ... +> In a continuous delivery world we are always ready to release, and as a release also include a changelog, or a release note, and other kind of documentation, these documents must also always be available continuously. .. we recognize that the good release note requires some manual work ... _so doing it continuously for every commit make missing work visible._ @@ -48,7 +48,7 @@ _Interfaces_ are mostly common data structures used to communicate between the m ## Testing and quality -Today we have a fair amount of tests on different levels in PAC, from unit tests, to functional tests and integration tests that interacts with real systems. +Today we have a fair amount of tests on different levels in PAC, from unit tests - that are not really unit tests, to functional tests and integration tests that interacts with real systems. When changing code, we have the following goals: