问题
I am currently writing REST API automation test scripts. As most of the research article suggests that we should write DAMP (Descriptive And Meaningful Phrases) tests that promote readability. However, I feel that there are a lot of duplicate codes in my tests and in an attempt to remove the duplicates I end up with 'DRY' (Don't repeat yourself) code which tends to dependency tests. So I am a bit confused about which approach to use? I would really appreciate it If anyone can give me some suggestions on this?
回答1:
My recommendations are:
- re-use payloads (JSON or XML) from files where possible
- sign-in flows that set an
Authorizationheader should be re-usable - do not combine API requests to different end-points into a re-usable
Scenario - even for the same end-point, for very different payloads (e.g. boundary / error conditions) use a separate
Scenariofor each - use
Scenario Outlinesfor data-driven tests
Also please refer this answer for a good example of what NOT to do: https://stackoverflow.com/a/54126724/143475
回答2:
A general rule is to keep the code related to the Test Objective DAMP, having everything else DRY. To simplify the rule, code related to the Test Objective may reference to:
Actions that DIRECTLY impact the expected result
Data parameters that DIRECTLY affect the expected result
Code NOT related to the Test Objective may reference to:
Actions that do not impact the expected result DIRECTLY (Example: authorization for the tests not related to login)
Configuration data and data parameters that does not affect the expected results DIRECTLY (Example: Base URL, login and password for the tests not related to authorization)
来源：https://stackoverflow.com/questions/60562263/dry-or-damp-which-one-is-efficient-in-api-automation-test-scripts