dongshan4549 2013-06-20 14:23
浏览 66
已采纳

我可以教PHPUnit Mage :: throwException *总是*抛出异常吗?

Magento has a static method that does some extra reporting just before throwing an exception.

/**
 * Throw Exception
 *
 * @param string $message
 * @param string $messageStorage
 * @throws Mage_Core_Exception
 */
public static function throwException($message, $messageStorage = null)
{
    if ($messageStorage && ($storage = self::getSingleton($messageStorage))) {
        $storage->addError($message);
    }
    throw new Mage_Core_Exception($message);
}

It's guaranteed to throw an exception, so it's mildly annoying that PHPUnit's code coverage considers the closing brace after a Mage::throwException statement to be uncovered code.

Shows code coverage analysis of code with no coverage following throwException statement.

I looked through the PHPUnit documentation, but I don't see any non-hacky way to have it consider the line covered. (I consider putting a dead-code return statement at the end of the method hacky, or really anything that we would have to do every time we use Mage::throwException.)

Is there some way I can teach PHPUnit that Mage::throwException always throws an exception, so treat it the same (with respect to coverage) as it would throw new WhateverException()?

  • 写回答

1条回答 默认 最新

  • dongyongyin5339 2014-05-30 14:11
    关注

    I have also this problem.

    Just do:

    throw Mage::getException(...);
    

    and in getException you return the exception object. Otherwise you're stuck with it.

    本回答被题主选为最佳回答 , 对您是否有帮助呢?
    评论

报告相同问题?

悬赏问题

  • ¥15 #MATLAB仿真#车辆换道路径规划
  • ¥15 java 操作 elasticsearch 8.1 实现 索引的重建
  • ¥15 数据可视化Python
  • ¥15 要给毕业设计添加扫码登录的功能!!有偿
  • ¥15 kafka 分区副本增加会导致消息丢失或者不可用吗?
  • ¥15 微信公众号自制会员卡没有收款渠道啊
  • ¥100 Jenkins自动化部署—悬赏100元
  • ¥15 关于#python#的问题:求帮写python代码
  • ¥20 MATLAB画图图形出现上下震荡的线条
  • ¥15 关于#windows#的问题:怎么用WIN 11系统的电脑 克隆WIN NT3.51-4.0系统的硬盘