caicloud / aloe Goto Github PK

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug
/kind feature

/kind feature

What happened:

Now test case can not be selected, all test cases should be run every time

What you expected to happen:

e.g.
go test --skip "time=slow"
go test --pick "type=get"

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

• Failure [100.219 seconds]

/Users/admin/go/src/github.com/caicloud/tenant-admin/vendor/github.com/caicloud/aloe/framework.go:48
  create.yaml: Test create a partition eventually create corresponding namespace and quota [It]
  /Users/admin/go/src/github.com/caicloud/tenant-admin/vendor/github.com/caicloud/aloe/framework.go:84

  Timed out after 100.001s.
  Expected
      <string>: 
  to match response: {
  status code is not matched, expected: 200, actual: 404
  api status: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"resourcequotas \"test-partition-123\" not found","reason":"NotFound","details":{"name":"test-partition-123","kind":"resourcequotas"},"code":404}
  
  }

should be print api real response when test fail

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug
/kind feature

What happened:

Call function in template is supported(e.g. ${ random(`regexp`) }) but the code is mess

What you expected to happen:

1. move all internal functions into one dir
2. support custom functions

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

/kind feature

What happened:
my test workflow:
1.user login return token
2.get the token for next request
my body struct :

{
    "success": true,
    "code": 0,
    "msg": "",
    "data": {
        "uid": 1000007,
        "login_name": "86:15810362016:3",
        "token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJleHAiOjE1NjgxMTYzNDEsImlzcyI6IkRpMjMwOXNsa2Q5OGE5OGFkaWFzZGxmMDlzZGdka2YyMWtqZ3Nka2YiLCJ1aWQiOjEwMDAwMDd9.VOLfK19uaRJuldeVPVe2wndpSZm1tpCxP65CRNUgyUk"
    }
}

What you expected to happen:
I want to set the token to definition.
how can i set ?

What is the issue about:

• add description

What happened:

What you expected to happen:

Anything else we need to know:

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug
/kind feature

/kind feature

What happened:

Sometimes we need to call API of different hosts with different tls config

What you expected to happen:

Different tls configs for different cases should be supported.

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Something else like tls config in http.Client also need to be supported.

• travis CI
• unit test
• coveralls

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own

/kind feature

What happened:

sometimes a random string or int is needed to generate different context

What you expected to happen:

1. add random key word

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Is this a BUG REPORT or FEATURE REQUEST?:

/kind feature

What happened:

flow:
- description: "Get user info in info.yaml"
  request:
    api: GET /user
    headers:
      "Authorization": "Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJleHAiOjE1NjY0NTgxNjAsImlzcyI6IkRpMjMwOXNsa2Q5OGE5OGFkaWFzZGxmMDlzZGdka2YyMWtqZ3Nka2YiLCJ1aWQiOjEwMDAwMDd9.Xff-abmUDYejaGMKI5r1gBEUSeLYu5ARboAAcjoEZ2g"
  response:
    statusCode: 200

What you expected to happen:

statusCode:200

Acture result

statusCode:400

Anything else we need to know?:
Is my headers set right or not?

req, err := http.NewRequest(method, "http://"+c.host+path, body)

now request hardcode in framework

i afraid my testcases not executed

➜  test git:(e2e_testcases) ✗ go test -v
=== RUN   TestPartitionAPI
Running Suite: API Suite
========================
Random Seed: 1514432621
Will run 1 of 1 specs

clean successfully
•
Ran 1 of 1 Specs in 0.267 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped --- PASS: TestPartitionAPI (0.27s)
PASS
ok  	github.com/caicloud/tenant-admin/test	0.350s

This issue is used for recording unclear failure messages

Template

expected or advice:

StatusCode is 404, expected is 200

actual:

StatusCode is 404

optional messages:

(log, picture, or anything else)

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind feature

What happened:

round trip flow should support condition and loop control

What you expected to happen:

1. add key word when
2. and key word loop

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug
/kind feature

What happened:

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug
/kind feature

/kind feature

What happened:

Now only one clean function can be used to clean up context

What you expected to happen:

1. each context can define its own clean function
2. each context can define its own preset function

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

use cases:

1. We only want to clean up the namespace which is created in the context
2. We want to get token and set into header for all requests in the context

when i list partition, this should be items, but follow testcases run successfully.

- description: "Try get partition eventually status"
  request:
    api: GET /api/v1/proxy/namespaces/default/services/tenant-admin:8080/apis/tenant.caicloud.io/v1alpha1/clusters/84984e39-57a7-4b8f-955e-127da0e46427/partitions
    headers:
      "Content-Type": "application/json"
    body: |
      {  
        "spec":{  
          "quota":{  
            "limits.cpu":"10m",
            "limits.memory":"10Mi",
            "requests.cpu":"10m",
            "requests.memory":"10Mi"
          },
          "tenant":"test-1234"
        },
        "status":{  
          "conditions":[  
            {  
              "status":"False",
              "type":"ExceedsQuota"
            }
          ],
          "hard":{
            "limits.cpu":"10m",
            "limits.memory":"180Mi",
            "requests.cpu":"10m",
            "requests.memory":"10Mi"
          },
          "phase":"Active",
          "used":{  
            "limits.cpu":"0",
            "limits.memory":"0",
            "requests.cpu":"0",
            "requests.memory":"0"
          }
        }
      }
  response:
    statusCode: 200
    eventually:
      timeout: "60s"
      interval: "1s"```