如何使用“Pex 和 Moles”带有实体框架的库？

发布于 2024-09-24 02:12:12 字数 2247 浏览 1 评论 0原文

这是一个困难，因为没有太多人使用 Pex 和 Pex。我认为 Moles 左右（尽管 Pex 是一款非常出色的产品 - 比任何其他单元测试工具都要好得多）

我有一个 Data 项目，它有一个非常简单的模型，只有一个实体 (DBItem）。我还在该项目中编写了一个 DBRepository 来操作此 EF 模型。存储库有一个名为 GetItems() 的方法，它返回业务层项目 (BLItem) 的列表，看起来与此类似（简化示例）：

public IList<BLItem> GetItems()
{
    using (var ctx = new EFContext("name=MyWebConfigConnectionName"))
    {
        DateTime limit = DateTime.Today.AddDays(-10);
        IList<DBItem> result = ctx.Items.Where(i => i.Changed > limit).ToList();
        return result.ConvertAll(i => i.ToBusinessObject());
    }
}

所以现在我想为此特定方法创建一些单元测试。我正在使用 Pex &鼹鼠。我为 EF 对象上下文创建了痣和存根。

我想编写参数化单元测试（我知道我首先编写了生产代码，但我必须这样做，因为我正在测试 Pex 和 Moles）来测试此方法是否返回有效的项目列表。

这是我的测试类：

[PexClass]
public class RepoTest
{
    [PexMethod]
    public void GetItemsTest(ObjectSet<DBItem> items)
    {
        MEFContext.ConstructorString = (@this, name) => {
             var mole = new SEFContext();
        };

        DBRepository repo = new DBRepository();
        IList<BLItem> result = repo.GetItems();

        IList<DBItem> manual = items.Where(i => i.Changed > DateTime.Today.AddDays(-10));

        if (result.Count != manual.Count)
        {
            throw new Exception();
        }
    }
}

然后我为这个特定的参数化单元测试运行Pex Explorations，但我收到错误超出路径范围。 Pex 通过向此测试方法提供 null 来启动此测试（因此 items = null）。这是 Pex 正在运行的代码：

[Test]
[PexGeneratedBy(typeof(RepoTest))]
[Ignore("the test state was: path bounds exceeded")]
public void DBRepository_GetTasks22301()
{
    this.GetItemsTest((ObjectSet<DBItem>)null);
}

这是 Pex 提供的附加注释：

测试用例对于这些输入来说运行时间太长，Pex 停止了分析。请注意：Oblivious.Data.Test.Repositories.TaskRepositoryTest.b__0 方法被调用了 50 次；请检查代码是否陷入无限循环或递归。否则，单击“Set MaxStack=200”，然后再次运行 Pex。
更新属性 [PexMethod(MaxStack = 200)]

问题

我这样做是否正确？我应该使用 EFContext 存根吗？我是否必须向测试方法添加其他属性，以便 Moles 主机能够运行（我不确定现在是否会运行）。我只运行 Pex &鼹鼠。没有 VS 测试或 nUnit 或其他任何东西。

我想我应该为 Pex 设置一些限制，让它为这个特定的测试方法提供多少项目。

原文

This is a tough one because not too many people use Pex & Moles or so I think (even though Pex is a really great product - much better than any other unit testing tool)

I have a Data project that has a very simple model with just one entity (DBItem). I've also written a DBRepository within this project, that manipulates this EF model. Repository has a method called GetItems() that returns a list of business layer items (BLItem) and looks similar to this (simplified example):

public IList<BLItem> GetItems()
{
    using (var ctx = new EFContext("name=MyWebConfigConnectionName"))
    {
        DateTime limit = DateTime.Today.AddDays(-10);
        IList<DBItem> result = ctx.Items.Where(i => i.Changed > limit).ToList();
        return result.ConvertAll(i => i.ToBusinessObject());
    }
}

So now I'd like to create some unit tests for this particular method. I'm using Pex & Moles. I created my moles and stubs for my EF object context.

I would like to write parametrised unit test (I know I've first written my production code, but I had to, since I'm testing Pex & Moles) that tests that this method returns valid list of items.

This is my test class:

[PexClass]
public class RepoTest
{
    [PexMethod]
    public void GetItemsTest(ObjectSet<DBItem> items)
    {
        MEFContext.ConstructorString = (@this, name) => {
             var mole = new SEFContext();
        };

        DBRepository repo = new DBRepository();
        IList<BLItem> result = repo.GetItems();

        IList<DBItem> manual = items.Where(i => i.Changed > DateTime.Today.AddDays(-10));

        if (result.Count != manual.Count)
        {
            throw new Exception();
        }
    }
}

Then I run Pex Explorations for this particular parametrised unit test, but I get an error path bounds exceeded. Pex starts this test by providing null to this test method (so items = null). This is the code, that Pex is running:

[Test]
[PexGeneratedBy(typeof(RepoTest))]
[Ignore("the test state was: path bounds exceeded")]
public void DBRepository_GetTasks22301()
{
    this.GetItemsTest((ObjectSet<DBItem>)null);
}

This was additional comment provided by Pex:

The test case ran too long for these inputs, and Pex stopped the analysis. Please notice: The method Oblivious.Data.Test.Repositories.TaskRepositoryTest.b__0 was called 50 times; please check that the code is not stuck in an infinite loop or recursion. Otherwise, click on 'Set MaxStack=200', and run Pex again.
Update attribute [PexMethod(MaxStack = 200)]

Question

Am I doing this the correct way or not? Should I use EFContext stub instead? Do I have to add additional attributes to test method so Moles host will be running (I'm not sure it does now). I'm running just Pex & Moles. No VS test or nUnit or anything else.

I guess I should probably set some limit to Pex how many items should it provide for this particular test method.

分享到QQ

分享到微博