CMS itself. The two applications are completely independent. They cannot make use of each other’s data or functionality. Let’s create the new Polls/CMS Integration application where we will bring them as _ class PollPluginPublisher(CMSPluginBase): model = PollPluginModel # model where plugin data are saved module = _("Polls") name = _("Poll Plugin") # name of the plugin in the interface _("Create Alias"), reverse("admin:cms_create_alias"), data={'plugin_id': plugin.pk, 'csrfmiddlewaretoken': get_token(request)}, ) ]

CMS itself. The two applications are completely independent. They cannot make use of each other’s data or functionality. Let’s create the new Polls/CMS Integration application where we will bring them plugin class PollPluginPublisher(CMSPluginBase): model = PollPluginModel # model where plugin data are saved module = _("Polls") name = _("Poll Plugin") # name of the plugin in the interface _("Create Alias"), reverse("admin:cms_create_alias"), data={'plugin_id': plugin.pk, 'csrfmiddlewaretoken': get_token(request)}, ) ]

CMS itself. The two applications are completely independent. They cannot make use of each other’s data or functionality. Let’s create the new Polls/CMS Integration application where we will bring them plugin class PollPluginPublisher(CMSPluginBase): model = PollPluginModel # model where plugin data are saved module = _("Polls") name = _("Poll Plugin") # name of the plugin in the interface _("Create Alias"), reverse("admin:cms_create_alias"), data={'plugin_id': plugin.pk, 'csrfmiddlewaretoken': get_token(request)}, ) ]

translation import ugettext as _ class CMSPollPlugin(CMSPluginBase): model = PollPlugin # model where plugin data are saved module = _("Polls") name = _("Poll Plugin") # name of the plugin in the interface render_template request, plugin): return [ PluginMenuItem( _("Create Alias"), reverse("admin:cms_create_alias"), data={'plugin_id': plugin.pk, 'csrfmiddlewaretoken': get_token(request)}, ) ] 5.2. How-to guides 39 django request, placeholder): return [ PluginMenuItem( _("Create Alias"), reverse("admin:cms_create_alias"), data={'placeholder_id': placeholder.pk, 'csrfmiddlewaretoken': get_token(request) ) ] def get_plugin_urls(self):

import ugettext as _ class CMSPollPlugin(CMSPluginBase): model = PollPlugin # model where plugin data are saved module = _("Polls") name = _("Poll Plugin") # name of the plugin in the interface render_template aldryn_apphooks_config.models import AppHookConfig from aldryn_apphooks_config.utils import setup_config from app_data import AppDataForm from django.db import models from django import forms from django.utils.translation provide a lot of useful methods to prepare the environment for our tests or to create useful test data. Submitting your code After the code and the tests are ready and packed in commits, you must submit

result['test_01']['url'] data = { 'key': result['test_01']['key'], 'city': result['test_01']['city'] } he={ 'Content-Type': 'application/x-www-form-urlencoded' } r = requests.post(url,headers=he,data=data) print(r FullLoader) case = result['case'] @pytest.mark.parametrize('data',case) def test_01(data): data = { 'key': data['key'], 'city': data['city'] } he={ 'Content-Type': 'application/x-www-form-urlencoded' encoded' } r = requests.post(result['url'],headers=he,data=data) print(r.text) 19 《51 测试天地》七十四 www.51testing.com 通过运行程序，我们可以很清楚的看到，两条数据同一个接口，均请求成功。 总结 小编通过两个简单的案例，进行介绍了Yaml在我们自动化测试过程中如何存储数据，

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593 4.10 Providing initial data for models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597 4.11 Django TemplateResponse and SimpleTemplateResponse . . . . . . . . . . . . . . . . . . . . . 1385 6.22 Unicode data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1389 model layer Django provides an abstraction layer (the “models”) for structuring and manipulating the data of your Web application. Learn more about it below: • Models: Introduction to models | Field types

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592 4.10 Providing initial data for models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596 4.11 Running TemplateResponse and SimpleTemplateResponse . . . . . . . . . . . . . . . . . . . . . 1350 6.22 Unicode data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1354 model layer Django provides an abstraction layer (the “models”) for structuring and manipulating the data of your Web application. Learn more about it below: • Models: Introduction to models | Field types

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598 4.10 Providing initial data for models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602 4.11 Running TemplateResponse and SimpleTemplateResponse . . . . . . . . . . . . . . . . . . . . . 1384 6.22 Unicode data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1387 model layer Django provides an abstraction layer (the “models”) for structuring and manipulating the data of your Web application. Learn more about it below: • Models: Introduction to models | Field types

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649 4.11 Providing initial data for models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654 4.12 Integrating TemplateResponse and SimpleTemplateResponse . . . . . . . . . . . . . . . . . . . . . . . . . 1562 6.23 Unicode data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1566 model layer Django provides an abstraction layer (the “models”) for structuring and manipulating the data of your Web application. Learn more about it below: • Models: Introduction to models | Field types