【问题标题】:How to test delete method如何测试删除方法
【发布时间】:2013-09-26 11:59:48
【问题描述】:

我的服务中有这个删除方法。

public boolean delete(Integer id) {
        Vacancy vacancy = vacancyDao.findById(id);
        return vacancy != null && vacancyDao.remove(vacancy);
    }

道实现:

@Override
    public boolean remove(Vacancy vacancy) throws HibernateException {
        Session session = sessionFactory.getCurrentSession();
        if (vacancy == null) {
            return false;
        }

        int result = session.createQuery("delete from Vacancy where id = :id")
                .setInteger("id", vacancy.getId()).executeUpdate();// place 1
        return result > 0;

    }

1 的地方我有classNotFoundException,我不在控制台中。休眠搜索“来自”类。

但是执行后result == 1.

为了测试我写了so方法

 @Test
 public void delete(){
            vacancyService.delete(vacancy.getId());

            sessionFactory.getCurrentSession().flush();

            Vacancy vacancyFromDb = vacancyService.findById(vacancy.getId());       

            Assert.assertNull(vacancyFromDb);
        }

在日志中我看到了

Hibernate: delete from vacancy where id=?

但在测试中我有异常:

java.lang.AssertionError: expected null, but was:<com.epam.hhsystem.model.vacancy.Vacancy@1>
    at org.junit.Assert.fail(Assert.java:88)
    at org.junit.Assert.failNotNull(Assert.java:664)
    at org.junit.Assert.assertNull(Assert.java:646)
    at org.junit.Assert.assertNull(Assert.java:656)
    at com.epam.hhhsystem.services.VacancyServiceTest.delete(VacancyServiceTest.java:72)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
    at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
    at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
    at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
    at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
    at org.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:74)
    at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
    at org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:83)
    at org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:72)
    at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:231)
    at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:88)
    at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
    at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
    at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
    at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
    at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
    at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
    at org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)
    at org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:71)
    at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
    at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:174)
    at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
    at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)

你能帮我做我想要的吗?

附言

VacancyService 标记为@Transactional

【问题讨论】:

    标签: java hibernate unit-testing jpa orm


    【解决方案1】:

    试试这个:

    Query query = session.createQuery("delete Vacancy vac where vac.id=:id");
    query.setInteger("id", id);
    query.executeUpdate();
    

    【讨论】:

      【解决方案2】:

      你可以只使用session.delete(),改变你的remove方法

      @Override
          public boolean remove(Vacancy vacancy) throws HibernateException {
              Session session = sessionFactory.getCurrentSession();
              if (vacancy == null) {
                  return false;
              }
      
              session.delete(vacancy);
              //delete method does not returns anything, implement some logic to 
              determine the result.
          }
      

      编辑: 检查您的transaction。 来自 Hibernate 文档

       Session sess = factory.openSession();
       Transaction tx;
       try {
           tx = sess.beginTransaction();
           //do some work
           ...
           tx.commit();
       }
       catch (Exception e) {
           if (tx!=null) tx.rollback();
           throw e;
       }
       finally {
           sess.close();
       }
      

      【讨论】:

      • 我知道,但我想知道我必须如何以普通方式制作
      • createQuery 接受hql,意味着Vacancy 应该是hibernate object 的名称,而不是table name。确保对象的名称是 Vacancy u 在您的休眠配置中配置。
      • 我确定已满。'return result > 0;'这里结果 == 1
      • 如果结果 == 1 我可以确定?
      • 那么你必须检查你的交易,可能它没有提交。
      猜你喜欢
      • 2021-12-13
      • 2019-10-03
      • 2015-06-05
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      • 2022-12-09
      相关资源
      最近更新 更多