manual test for deploy-from-file

Author: cheld

docs/test/deploy-from-file.md

@@ -0,0 +1,29 @@
+# Deploy from file
+
+## Prerequisites
+Open deploy dialog (+) and select "Upload a YAML or JSON file"
+
+## Expected result at execution
+* In positive case the "Deploy" button must lead to the creation of a running application
+* Validation errors affecting particular fields must be displayed beneath these fields. In case the deployment  fails due to an exception, then a pop dialog is shown
+
+## Specific factors
+
+| Factor       | 1                            | 2                      | 3                                           | 4                | 5            | 6                             | 7                       | Comment |
+|--------------|------------------------------|------------------------|---------------------------------------------|------------------|--------------|-------------------------------|-------------------------|---------|
+| File name    | Empty                        | Short                  | Max-length                                  |                  |              |                               |                         |         |
+| File content | Correct YAML, e.g. Guestbook | Correct JSON           | Binary, e.g. PNG                            | Validation error | Syntax error | no RC, e.g. Only pod, svc,... | Special chars, e.g. XSS |         |
+| Existence    | Empty cluster                | Deploy same file twice | One resource already exists, e.g. Namespace |                  |              |                               |                         |         |
+| Action       | "Deploy"                     | "Cancel"               |                                             |                  |              |                               |                         |         |
+
+## Common Factors
+
+| Factor          | 1                          | 2                                | 3  | 4      |
+|-----------------|----------------------------|----------------------------------|----|--------|
+| Browser         | Chrome                     | Firefox                          | IE | Safari |
+| Form            | Desktop                    | Mobile                           |    |        |
+| Help            | Hover over every?          | Click on every "Learn more" link |    |        |
+| Log entries     | check log entry on success | Check log entry on failure       |    |        |
+| Success message | Shown for every action     |                                  |    |        |
+| Failure message | Proper sentence            |                                  |    |        |
+| Concurrency     | UI refreshes after error   |                                  |    |        |

docs/test/readme.md

@@ -0,0 +1,28 @@
+# Manual Testing
+
+In this project we do manual testing with an approach that is called factor based testing (FBT)
+
+## Process of Defining Test Sheets
+
+A test sheet is defined for every test area. Typically a test area is a UI page.
+The test area is examined. All actions and potential errors are grouped into test factors. (Take a look at the existing test sheets).
+
+The test factors are divided into specific factors that apply only to the test area and common test factors that apply to all areas. Scratched factors will not be implemented in first release.
+
+## Process of Testing
+
+Pick a test sheet and study the specific and the common factors. The common factors are defined in a generic way. They might need some mental adaption to your test area.
+
+Consider the test factors as a cheat-sheet or checklist. They should foster your creativity when doing tests. Think about combining multiple test factors in 'evil' test scenarios.
+
+
+The factors do not define an expected outcome. This is intentional.
+The following can help you to decide if the observed behavior is a bug:
+* Compare it with other areas. It must be consistent within Dashboard.
+* Compare it with other large websites like Gmail or Inbox. These sites follow common practices and match user expectation.
+
+Dashboard is under constant development. Always enhance and adopt the sheets when doing tests. 
+
+## Sheets
+
+* [Deploy from file](deploy-from-file.md)