Commit 42c6066e authored by 邓莹莹's avatar 邓莹莹

Merge branch 'common_dev' into 'master'

Common dev

See merge request dengyingying/backend_auto!2
parents 53e820b5 f8103557
......@@ -2,7 +2,7 @@ import path_setting
from in_common.base_request import BaseRequest
class send_reqest(BaseRequest):
class account_request(BaseRequest):
def __init__(self):
self.data = self.api_load(path_setting.APYAML_CONFIG)
......@@ -16,4 +16,4 @@ class send_reqest(BaseRequest):
if __name__ == '__main__':
print(send_reqest().login_vfc("beijing", "+8612345678912", 1234, "", ""))
\ No newline at end of file
print(account_request().login_vfc("beijing", "+8612345678912", 1234, "", ""))
\ No newline at end of file
......@@ -9,10 +9,13 @@
### 提交代码规范
- 为了便于项目的管理维护,参与者可以将自己的代码确保运行成功的前提下,提交到自己分支,然后每周往commo_dev
分支提交代码,负责人会将common_dev分支每周往master分支合并,参与者可每周一更新本地代码,确保自己的代码是最新的
- 本地代码提交Git仓库时,避免已经上传的代码被覆盖,请Git push之前,先操作git pull,在本地解决好冲突后,再Git push
### 项目分类及维护
- 项目围绕backend进行自动化测试,所以针对项目的分类以及命名,大家尽量以下面的规则维护
![](.readme_images/all_backend_api中Py文件class命名.png)
!![](.readme_images/项目all_backend_api命名规则.png)
![](.readme_images/test_case命名规则.png)
......
......@@ -8,6 +8,7 @@ jsonpath==0.82
packaging==20.9
pluggy==0.13.1
py==1.10.0
pyparsing==2.4.7
pytest==6.2.2
PyYAML==5.4.1
......
......@@ -3,7 +3,7 @@ import pytest
from ids_list import get_ids
import path_setting
from in_common.base_request import BaseRequest
from all_backend_api.account_request import send_reqest
from all_backend_api.account_request import account_request
class TestLoginVfc:
......@@ -13,7 +13,7 @@ class TestLoginVfc:
@pytest.mark.parametrize("param",loginvfc_data,ids=loginvfc_case)
def test_login_vfc(self,param):
print(param["vfc_code"])
r = send_reqest().login_vfc(param["current_city_id"], param["phone_num"], param["vfc_code"])
r = account_request().login_vfc(param["current_city_id"], param["phone_num"], param["vfc_code"])
if r["error"] == 0:
assert r["data"]["account_phone"] == param["assert"]
if r["error"] == 1:
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment