archive/rsnext

Fork 0

Commit graph

Author	SHA1	Message	Date
JJ Kasper	7d0919a784	Break up basic test suite (#6730 ) * Break out client-navigation and rendering test from basic test * Try with parallelism dialed back to 3 * Update jest-junit for more compatible timings in CircleCI * Bump to test timings * Use filepath for suitename in jest-junit * Store reports as artifacts * Try using classname for timings * Bump * Remove reports from artifacts	2019-03-20 11:01:32 +01:00
Michael Fix	9532cc1256	Remove old UNSAFE_ lifecycle methods (#5020 ) ~I am not sure if this is a valid fix yet, but I was going to let CI run the tests for me. I'll close and look into it if the build fails.~ Let me know if this will cause issues, but I don't think it should. The React docs recommends moving `componentWillMount` logic into the constructor	2018-08-25 17:26:11 +02:00

Author

SHA1

Message

Date

JJ Kasper

7d0919a784

Break up basic test suite (#6730 )

* Break out client-navigation and rendering
test from basic test

* Try with parallelism dialed back to 3

* Update jest-junit for more compatible timings in CircleCI

* Bump to test timings

* Use filepath for suitename in jest-junit

* Store reports as artifacts

* Try using classname for timings

* Bump

* Remove reports from artifacts

2019-03-20 11:01:32 +01:00

Michael Fix

9532cc1256

Remove old UNSAFE_ lifecycle methods (#5020 )

~I am not sure if this is a valid fix yet, but I was going to let CI run the tests for me. I'll close and look into it if the build fails.~

Let me know if this will cause issues, but I don't think it should. The React docs recommends moving `componentWillMount` logic into the constructor

2018-08-25 17:26:11 +02:00

2 commits