Keep them separate. A unit test is supposed to tell you which unit failed. Keeping them separate also allows you to isolate the problem quickly w/o requiring you to go through a lengthy debug cycle.
More Related Contents:
- How to run JUnit test cases from the command line
- How to test my servlet using JUnit
- Configuring IntelliJ IDEA for unit testing with JUnit
- Run JUnit tests with SBT
- How do I test a class that has private methods, fields or inner classes?
- What is Mocking?
- What’s the difference between unit tests and integration tests? [duplicate]
- What is the purpose of mock objects?
- Assert equals between 2 Lists in Junit
- What is unit testing and how do you do it? [duplicate]
- How to test that no exception is thrown?
- What are the differences between unit tests, integration tests, smoke tests, and regression tests? [closed]
- Multiple RunWith Statements in jUnit
- How to Unit Test React-Redux Connected Components?
- Fill os.Stdin for function that reads from it
- How to use JUnit to test asynchronous processes
- AssertEquals 2 Lists ignore order
- java.lang.IllegalAccessError: Class ref in pre-verified class resolved to unexpected implementation getting while running test project?
- Junit5 mock a static method
- Unit-testing servlets [closed]
- Service mocked with Jest causes “The module factory of jest.mock() is not allowed to reference any out-of-scope variables” error
- How to unit test a Go Gin handler function?
- java.lang.NoClassDefFoundError in junit
- Is there an easy way to stub out time.Now() globally during test?
- Unit testing a method that calls another method
- how to export (JUnit) test suite as executable jar
- AndroidManifest in androidTest directory being ignored
- Testing route configuration in ASP.NET WebApi
- how do I mock sqlconnection or should I refactor the code?
- How to test methods that call System.exit()?