wintercms/winter:

代码拉取完成,页面将自动刷新

richgiteeai

Watch

不关注关注所有动态仅关注版本发行动态关注但不提醒动态

1 Star 0 Fork 0

wintercms/winter

代码 Issues 0 Pull Requests 0 Wiki 统计流水线

服务

加入 Gitee

与超过 1400万开发者一起发现、参与优秀开源项目,私有仓库也完全免费 :)

免费加入

已有帐号? 立即登录

文件

新建文件新建 Diagram 文件

develop

分支 (30)

标签 (165)

管理

develop

wip/1.2

wip/1.2-mirror-ehancements

wip/list-controller-reorder-mode

wip/1.2-code-analysis

wip/inspector-rewrite

wip/config-write-replacement

wip/1.2-revise-class-loader

wip/restore-laravel-mailer-behavior

1.0

1.1

wip/improve-exceptions

wip/cms-page-router-optimise

wip/tweak-test-cmd

wip/db-media-items

fix/resize-on-replacement

wip/maintenance-ip-whitelist

wip/branding-config

wip/rebrand-branding-defaults

uninstall-all-plugins

v1.1.8

v1.1.7

v1.0.474

v1.1.6

v1.1.5

v1.1.4

v1.1.3

v1.0.473

v1.1.2

v1.0.472

v1.1.1

v1.0.471

v1.0.470

v1.1.0

v1.0.469

v1.0.468

v1.0.467

v1.0.466

v1.0.465

v1.0.463

克隆/下载

HTTPS SSH SVN SVN+SSH 下载ZIP

提示

下载代码请复制以下命令到终端执行

为确保你提交的代码身份被 Gitee 正确识别,请执行以下命令完成配置

git config --global user.name userName 
git config --global user.email userEmail

初次使用 SSH 协议进行代码克隆、推送等操作时,需按下述提示完成 SSH 配置

1 生成 RSA 密钥

2 获取 RSA 公钥内容,并配置到 SSH公钥中

在 Gitee 上使用 SVN,请访问使用指南

使用 HTTPS 协议时,命令行会出现如下账号密码验证步骤。基于安全考虑,Gitee 建议配置并使用私人令牌替代登录密码进行克隆、推送等操作

Username for 'https://gitee.com': userName

Password for 'https://userName@gitee.com': # 私人令牌

新建文件新建 Diagram 文件

分支 30

标签 165

贡献代码

同步代码

创建 Pull Request

了解更多

对比差异通过 Pull Request 同步

同步更新到分支

通过 Pull Request 同步

将会在向当前分支创建一个 Pull
Request,合入后将完成同步

Ben Thomson Fix view maker unit test for Windows 3ff0360

6086 次提交

File empty ...

concerns

fixtures

unit

PluginTestCase.php

README.md

TestCase.php

bootstrap.php

README

# Plugin testing

Individual plugin test cases can be run by running `../../../vendor/bin/phpunit` in the plugin's base directory (ex. `plugins/acme/demo`.

### Creating plugin tests

Plugins can be tested by creating a file called `phpunit.xml` in the base directory with the following content, for example, in a file **/plugins/acme/blog/phpunit.xml**:

<?xml version="1.0" encoding="UTF-8"?>
 <phpunit backupGlobals="false"
 backupStaticAttributes="false"
 bootstrap="../../../tests/bootstrap.php"
 colors="true"
 convertErrorsToExceptions="true"
 convertNoticesToExceptions="true"
 convertWarningsToExceptions="true"
 processIsolation="false"
 stopOnFailure="false"
 syntaxCheck="false"
 >
 <testsuites>
 <testsuite name="Plugin Unit Test Suite">
 <directory>./tests</directory>
 </testsuite>
 </testsuites>
 <php>
 <env name="APP_ENV" value="testing"/>
 <env name="CACHE_DRIVER" value="array"/>
 <env name="SESSION_DRIVER" value="array"/>
 </php>
 </phpunit>

Then a **tests/** directory can be created to contain the test classes. The file structure should mimic the base directory with classes having a `Test` suffix. Using a namespace for the class is also recommended.

<?php namespace Acme\Blog\Tests\Models;

use Acme\Blog\Models\Post;
 use PluginTestCase;

class PostTest extends PluginTestCase
 {
 public function testCreateFirstPost()
 {
 $post = Post::create(['title' => 'Hi!']);
 $this->assertEquals(1, $post->id);
 }
 }

The test class should extend the base class `PluginTestCase` and this is a special class that will set up the Winter database stored in memory, as part of the `setUp` method. It will also refresh the plugin being tested, along with any of the defined dependencies in the plugin registration file. This is the equivalent of running the following before each test:

php artisan winter:up
 php artisan plugin:refresh Acme.Blog
 [php artisan plugin:refresh <dependency>, ...]

> **Note:** If your plugin uses [configuration files](../plugin/settings#file-configuration), then you will need to run `System\Classes\PluginManager::instance()->registerAll(true);` in the `setUp` method of your tests. Below is an example of a base test case class that should be used if you need to test your plugin working with other plugins instead of in isolation.

use System\Classes\PluginManager;

class BaseTestCase extends PluginTestCase
 {
 public function setUp(): void
 {
 parent::setUp();

// Get the plugin manager
 $pluginManager = PluginManager::instance();

// Register the plugins to make features like file configuration available
 $pluginManager->registerAll(true);

// Boot all the plugins to test with dependencies of this plugin
 $pluginManager->bootAll(true);
 }

public function tearDown(): void
 {
 parent::tearDown();

// Get the plugin manager
 $pluginManager = PluginManager::instance();

// Ensure that plugins are registered again for the next test
 $pluginManager->unregisterAll();
 }
 }

#### Changing database engine for plugins tests

By default Winter CMS uses SQLite stored in memory for the plugin testing environment. If you want to override the default behavior set the `useConfigForTesting` config to `true` in your `/config/database.php` file. When the `APP_ENV` is `testing` and the `useConfigForTesting` is `true` database parameters will be taken from `/config/database.php`.

You can override the `/config/database.php` file by creating `/config/testing/database.php`. In this case variables from the latter file will be taken.

## System testing

To perform unit testing on the core Winter files, you should download a development copy using composer or cloning the git repo. This will ensure you have the `tests/` directory.

### Unit tests

Unit tests can be performed by running `vendor/bin/phpunit` in the root directory of your Winter CMS installation.

### Functional tests

Functional tests can be performed by installing the [Winter.Dusk](https://wintercms.com/plugin/winter-dusk) in your Winter CMS installation. The Winter.Dusk plugin is powered by Laravel Dusk, a comprehensive testing suite for the Laravel framework that is designed to test interactions with a fully operational Winter CMS instance through a virtual browser.

For information on installing and setting up your Winter CMS install to run functional tests, please review the [README](https://github.com/wintercms/wn-dusk-plugin/blob/master/README.md) for the plugin.