Skip to content

Conversation

@Ayybeeshafi
Copy link
Contributor

@Ayybeeshafi Ayybeeshafi commented Jan 20, 2019

I figured out that failing of test is not random. Whichever testcase succeeded DashboardOverviewComponent should create failed.
We are using RouterModule in this testcase. I presume that this component couldn't be removed before next test or something like that.
My solution for this problem was calling
fixture.destroy() in afterEach in spec of DashboardOverviewComponent.
Tests are executing fine on the build pipeline as well as my machine.

@ghost ghost assigned Ayybeeshafi Jan 20, 2019
@ghost ghost added the review label Jan 20, 2019
@codecov-io
Copy link

Codecov Report

❗ No coverage uploaded for pull request base (develop@08fdb6e). Click here to learn what that means.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##             develop    #100   +/-   ##
=========================================
  Coverage           ?   4.69%           
=========================================
  Files              ?      11           
  Lines              ?     213           
  Branches           ?      15           
=========================================
  Hits               ?      10           
  Misses             ?     203           
  Partials           ?       0

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 08fdb6e...a4aea52. Read the comment docs.

Copy link
Contributor

@janniclas janniclas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hey @Ayybeeshafi ,
thanks for the research it's good to know there is at least some "consistency" in the failing tests.
About the dashboard-overview component and its tests. I'm a little bit confused here why we test with the angular router here in the first place. If I'm not mistaken the router-outlet is only explicitly used in the dashboard component.
Now I wonder if we actually might need the Angular RouterTesting module only in the dashboard component or also in every component where we do some routing? But anyways I believe it should definitely be added to the dashboard component where we actually use the router-outlet, do you agree?
Could you please have a look at these questions? :)

@ghost ghost assigned janniclas Jan 21, 2019
@janniclas janniclas merged commit 0eb0d4c into develop Jan 22, 2019
@ghost ghost removed the review label Jan 22, 2019
@janniclas janniclas deleted the inconsistent-tests branch January 24, 2019 14:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants