承接 ta-tikoma/phpunit-architecture-test 相关项目开发

从需求分析到上线部署,全程专人跟进,保证项目质量与交付效率

邮箱:yvsm@zunyunkeji.com | QQ:316430983 | 微信:yvsm316

ta-tikoma/phpunit-architecture-test

Composer 安装命令:

composer require --dev ta-tikoma/phpunit-architecture-test

包简介

Methods for testing application architecture

README 文档

README

Idea: write architecture tests as well as feature and unit tests. Protect your architecture code style!

Example

Don't use repositories in controllers use only in services classes. Take three layers "repositories", "services", "controllers" and add asserts on dependencies.

$controllers  = $this->layer()->leaveByNameStart('App\\Controllers');
$services     = $this->layer()->leaveByNameStart('App\\Services');
$repositories = $this->layer()->leaveByNameStart('App\\Repositories');

$this->assertDoesNotDependOn($controllers, $repositories);
$this->assertDependOn($controllers, $services);
$this->assertDependOn($services, $repositories);

Installation

Install via composer

composer require --dev ta-tikoma/phpunit-architecture-test

Add trait to Test class

abstract class TestCase extends BaseTestCase
{
    use ArchitectureAsserts;
}

Use

  • Create test
  • Make layers of application
  • Add asserts
    public function test_make_layer_from_namespace()
    {
        $app = $this->layer()->leaveByNameStart('PHPUnit\\Architecture');
        $tests = $this->layer()->leaveByNameStart('tests');

        $this->assertDoesNotDependOn($app, $tests);
        $this->assertDependOn($tests, $app);
    }

Run

./vendor/bin/phpunit

Test files structure

  • tests
    • Architecture
      • SomeTest.php
    • Feature
    • Unit

How to build Layer

  • $this->layer() take access to layer with all objects and filter for create your layer:
    • leave objects in layer only:
      • ->leave($closure) by closure
      • ->leaveByPathStart($path) by object path start
      • ->leaveByNameStart($name) by object name start
      • ->leaveByNameRegex($name) by object name regex
      • ->leaveByType($name) by object type
    • remove objects from layer:
      • ->exclude($closure) by closure
      • ->excludeByPathStart($path) by object path start
      • ->excludeByNameStart($name) by object name start
      • ->excludeByNameRegex($name) by object name regex
      • ->excludeByType($name) by object type
  • you can create multiple layers with split:
    • ->split($closure) by closure
    • ->splitByNameRegex($closure) by object name

Asserts

Dependencies

Example: Controllers don't use Repositories only via Services

  • assertDependOn($A, $B) Layer A must contains dependencies by layer B.
  • assertDoesNotDependOn($A, $B) Layer A (or layers in array A) must not contains dependencies by layer B (or layers in array B).

Methods

  • assertIncomingsFrom($A, $B) Layer A must contains arguments with types from Layer B
  • assertIncomingsNotFrom($A, $B) Layer A must not contains arguments with types from Layer B
  • assertOutgoingFrom($A, $B) Layer A must contains methods return types from Layer B
  • assertOutgoingNotFrom($A, $B) Layer A must not contains methods return types from Layer B
  • assertMethodSizeLessThan($A, $SIZE) Layer A must not contains methods with size less than SIZE

Properties

  • assertHasNotPublicProperties($A) Objects in Layer A must not contains public properties

Essence

You can use $layer->essence($path) method for collect data from layer. For example get visibility of all properties in layer: $visibilities = $layer->essence('properties.*.visibility'); .

  • assertEach($list, $check, $message) - each item of list must passed tested by $check-function
  • assertNotOne($list, $check, $message) - not one item of list must not passed tested by $check-function
  • assertAny($list, $check, $message) - one or more item of list must not passed tested by $check-function

Alternatives

Advantages

  • Dynamic creation of layers by regular expression (not need declare each module)
  • Run along with the rest of tests from phpunit
  • Asserts to method arguments and return types (for check dependent injection)
  • Asserts to properties visibility

ta-tikoma/phpunit-architecture-test 适用场景与选型建议

ta-tikoma/phpunit-architecture-test 是一款 基于 PHP 开发的 Composer 扩展包,目前已累计 56.35M 次下载、GitHub Stars 达 107, 最近一次更新时间为 2021 年 10 月 28 日, 在 PHP 生态内属于活跃度较高的组件。

它主要适用于以下技术方向: 「testing」 「phpunit」 「test」 「architecture」 「stucture」 等业务场景。在实际项目中,围绕这些方向常见需要落地的问题包括:接口对接、性能调优、并发安全、与既有框架(Laravel / ThinkPHP / Yii / Webman 等)的兼容适配,以及生产环境的日志埋点与稳定性保障。

我们在过去多个企业项目中使用过 ta-tikoma/phpunit-architecture-test 或与其功能相近的方案,如果你在选型或落地过程中遇到问题,例如 版本兼容、二次改造、私有化封装、与内部系统对接、生产 BUG 排查,欢迎联系我们协助评估。

围绕 ta-tikoma/phpunit-architecture-test 我们能提供哪些服务?
定制开发 / 二次开发

基于 ta-tikoma/phpunit-architecture-test 在你已有业务上做功能扩展、字段裁剪、UI 适配、与内部账号 / 权限 / 日志系统的深度对接。

BUG 修复 & 性能优化

线上偶发问题、内存泄漏、慢查询、并发异常等排查修复;针对高流量场景做缓存、队列、索引层面的调优。

项目外包 & 长期维护

承接完整的项目从需求 → 设计 → 开发 → 上线 → 长期运维;也可按月提供技术保姆服务。

yvsm@zunyunkeji.com QQ:316430983 微信:yvsm316 西安尊云信息科技 · 专注 PHP / Go / 分布式系统研发

统计信息

  • 总下载量: 56.35M
  • 月度下载量: 0
  • 日度下载量: 0
  • 收藏数: 107
  • 点击次数: 22
  • 依赖项目数: 12
  • 推荐数: 1

GitHub 信息

  • Stars: 107
  • Watchers: 4
  • Forks: 12
  • 开发语言: PHP

其他信息

  • 授权协议: MIT
  • 更新时间: 2021-10-28