Commit b042f98 Remove FAQ and README files from behave tests

2 files Authored and Committed by esakaiev a year ago
Remove FAQ and README files from behave tests

    
FAQ -18
 1 @@ -1,18 +0,0 @@
 2 - Q: How to download latest RPMs from nightly?
 3 - A: curl --silent http://ci.dnf.baseurl.org/job/nightly-fedora-24-x86_64/lastStableBuild/consoleText | grep "^https://copr.*\.rpm" | xargs wget
 4 - 
 5 - Q: I have patches for multiple projects (libhif, dnf, dnf-plugins-core), how do I build RPMs with those?
 6 - A: Not that trivial, but possible!
 7 -    0. You need to have working rpm-gitoverlay (find instructions at https://github.com/ignatenkobrain/rpm-gitoverlay#installation)
 8 -    1. Copy overlays/dnf-master/overlay.yml and edit it (remove unneded components, add branch tags, etc.)
 9 -    2. Build (S)RPM(s): https://github.com/ignatenkobrain/rpm-gitoverlay#usage
10 -       2.1. To use existing git repositories, use --gitdir option
11 -       2.2. To build just SRPM(s): rpm-gitoverlay build-overlay srpm
12 -       2.3. To build RPM(s): rpm-gitoverlay build-overlay rpm [BUILDER], where builder is copr/rpmbuild with some additional parameters (see -h/--help)
13 - 
14 - Q: I have RPMs, how do I run functional/integration tests locally?
15 - A: Easily!
16 -    1. Put your RPMs into "rpms" directory in repo
17 -    2. CONTAINER=$(./dnf-testing.sh build)
18 -    3. ./dnf-testing.sh run -c $CONTAINER
19 -    X. See ./dnf-testing.sh --help
  1 @@ -1,152 +0,0 @@
  2 - ci-dnf-stack
  3 - ============
  4 - 
  5 - ci-dnf-stack is a set of configuration and scripts that allow continuous
  6 - integrations DNF (https://github.com/rpm-software-management/dnf) stack.
  7 - 
  8 - This serves as an ad hoc solution to where to store routines that belong
  9 - to all the components of the stack. It would be nice to merge them into
 10 - the respective components.
 11 - 
 12 - These scripts are free and open-source software; see the section License
 13 - to understand the terms and conditions under which you can use, study,
 14 - modify and distribute ci-dnf-stack.
 15 - 
 16 - Dnf Docker Test in ci-dnf-stack
 17 - -------------------------------
 18 - 
 19 - The project originated from richdeps-docker (https://github.com/shaded-enmity/richdeps-docker).
 20 - Docker image for testing rich dependencies and CLI in DNF/RPM
 21 - using the Behave framework. The project was optimized for incorporation to
 22 - ci-dnf-stack as a module.
 23 - Each test runs in it's own container making it possible to run multiple tests
 24 - in parallel without interfering with each other. These tests are meant to
 25 - verify that both DNF and RPM (if relevant) interpret the rich dependency semantics
 26 - correctly and all functionality of DNF and related component is intact. Dnf Docker
 27 - Test use its own feature files and steps descriptions placed in its directory
 28 - (dnf-docker-test/).
 29 - 
 30 - License
 31 - -------
 32 - 
 33 - The project is licensed under the copyleft GNU General Public License;
 34 - either version 2, or (at your option) any later version. See the
 35 - LICENSE file found in the top-level directory of this distribution and
 36 - at https://github.com/rpm-software-management/ci-dnf-stack/. No part of
 37 - ci-dnf-stack, including this file, may be copied, modified, propagated,
 38 - or distributed except according to the terms contained in the LICENSE
 39 - file.
 40 - 
 41 - Requirements
 42 - ------------
 43 - 
 44 - * python
 45 - * python3 >= 3.5
 46 - * jenkins
 47 - * docker
 48 - * git-core
 49 - * /usr/bin/rpmbuild
 50 - * docker
 51 - * jq
 52 - 
 53 - For building in COPR:
 54 - * python3-copr
 55 - * python3-beautifulsoup4
 56 - * python3-requests
 57 - 
 58 - sudo should be configured for `jenkins` user to use `docker`:
 59 - ```
 60 - # cat << EOF > /etc/sudoers.d/99-jenkins
 61 - jenkins ALL=(ALL) NOPASSWD: /usr/bin/docker
 62 - EOF
 63 - ```
 64 - 
 65 - To rebuild `test-1` or `upgrade_1` repository for Dnf Docker Test run
 66 - `test-1.py` or `upgrade_1.py` in `dnf-docker-test/repo_create directory`.
 67 - It requires following components:
 68 - * python3-rpmfluff
 69 - 
 70 - Configuring Jenkins
 71 - -------------------
 72 - 
 73 - We are using [jenkins-job-builder](http://docs.openstack.org/infra/jenkins-job-builder/)
 74 - to manage jenkins jobs.
 75 - 
 76 - To deploy jobs you need configure your [jenkins_jobs.ini](http://docs.openstack.org/infra/jenkins-job-builder/execution.html)
 77 - and run `jenkins-jobs --config=/path/to/jenkins_jobs.ini update jobs/`.
 78 - 
 79 - Local run
 80 - ---------
 81 - 
 82 - Local test can be performed with dnf-testing.sh
 83 - * Container build:
 84 - ** Put your RPMs into "dnf-docker-test/rpms" directory
 85 - ** Then run ``dnf-testing.sh build``
 86 - * Run tests
 87 - ** Run all tests with last built container use command ``./dnf-testing.sh run``
 88 - ** Run all tests with specified container use command``./dnf-testing.sh run -c <CONTAINER>``
 89 - ** Run particular tests run: ``./dnf-testing.sh run TEST-A TEST-B ...``
 90 - * Run in devel mode
 91 - ** It shares local feature dir with description of tests and test steps with docker image, therefore you can develop CI stack on fly.
 92 - ** Use command ``./dnf-testing.sh run --devel $CONTAINER TEST-A``
 93 - * Get help
 94 - ** ./dnf-testing.sh --help
 95 - 
 96 - 
 97 - Describing a test
 98 - -----------------
 99 - 
100 - Here's an example configuration from the first ported test:
101 - 
102 - ```
103 - Feature: Install package with dependency
104 - 
105 -     @setup
106 -     Scenario: Feature setup
107 -         Given repository "test" with packages
108 -            | Package | Tag      | Value |
109 -            | TestA   | Requires | TestB |
110 -            | TestB   |          |       |
111 - 
112 -     Scenario: Install TestA from repository "test" with dependency TestB
113 -          When I save rpmdb
114 -           And I enable repository "test"
115 -           And I successfully run "dnf install -y TestA" with "success"
116 -          Then rpmdb changes are
117 -            | State     | Packages     |
118 -            | installed | TestA, TestB |
119 - ```
120 - 
121 - Possible states: installed, removed, absent, unchanged, reinstalled, updated, downgraded.
122 - The states unchanged and absent can be used
123 - for detailed description of tested step or to ensure, that required conditions before or after tested step were met.
124 - 
125 - Support
126 - -------
127 - 
128 - If you are having issues, please report them via the issue tracking
129 - system.
130 - 
131 - - issue tracker: https://github.com/rpm-software-management/ci-dnf-stack/issues
132 - 
133 - Notes for functional testing
134 - ----------------------------
135 - 
136 - Repo upgrade_1:
137 - updateinfo.xml was added using modifyrepo_c updateinfo.xml path/upgrade_1/repodata/
138 - 
139 - Repo test-1-gpg:
140 - Was created from rpms in test-1 repo. All rpm were signed with gpg-pubkey-2d2e7ca3-56c1e69d»       gpg(DNF Test1 (TESTER)
141 - <dnf@testteam.org>) except TestE (not signed), TestG (signed with key gpg-pubkey-705f3e8c-56c2e298»       gpg(DNF Test2
142 - (TESTER) <dnf@testteam.org>)), and TestJ (not signed and incorrect check-sum).
143 - 
144 - Repo upgrade_1-gpg:
145 - Was created from rpms in upgrade_1 repo. All rpm were signed with gpg-pubkey-705f3e8c-56c2e298»       gpg(DNF Test2
146 - (TESTER) <dnf@testteam.org>) except both TestE (not signed) packages.
147 - 
148 - Contributions
149 - -------------
150 - 
151 - Any contribution or feedback is more than welcome.
152 - 
153 - - version control system: https://github.com/rpm-software-management/ci-dnf-stack