Created
June 23, 2017 14:39
-
-
Save pahund/b5269b470a7008180c6fecef2ca23062 to your computer and use it in GitHub Desktop.
Wallaby.js Failing Tests
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| 62 failing tests, 1197 passing | |
| test/server/services/OptimizelyTest.js [server/services/Optimizely] When I instantiate a Optimizely service and the Optimizely API cannot be reached and I call the “fetch” method the “data” property is not set [12 ms] | |
| Error: nope | |
| at setup test/server/services/OptimizelyTest.js:308 | |
| at Context.<anonymous> test/server/services/OptimizelyTest.js:217 | |
| From console: | |
| (node:12929) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 19) | |
| test/server/services/OptimizelyTest.js [server/services/Optimizely] When I instantiate a Optimizely service and the Optimizely API cannot be reached and I call the “fetch” method and I try to get variants an error is thrown because no data was fetched [3 ms] | |
| Error: nope | |
| at setup test/server/services/OptimizelyTest.js:308 | |
| at Context.<anonymous> test/server/services/OptimizelyTest.js:217 | |
| From console: | |
| (node:12929) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 21) | |
| test/server/services/OptimizelyTest.js [server/services/Optimizely] When I instantiate a Optimizely service and the Optimizely API cannot be reached and I call the “fetch” method the “get optimizely data” utility function is called with the correct URL [5 ms] | |
| Error: nope | |
| at setup test/server/services/OptimizelyTest.js:308 | |
| at Context.<anonymous> test/server/services/OptimizelyTest.js:217 | |
| From console: | |
| (node:12929) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 15) | |
| test/server/services/OptimizelyTest.js [server/services/Optimizely] When I instantiate a Optimizely service and the Optimizely API cannot be reached and I call the “fetch” method the “get optimizely data” utility function is called with the correct logger [3 ms] | |
| Error: nope | |
| at setup test/server/services/OptimizelyTest.js:308 | |
| at Context.<anonymous> test/server/services/OptimizelyTest.js:217 | |
| From console: | |
| (node:12929) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 17) | |
| test/server/services/OptimizelyTest.js [server/services/Optimizely] When I instantiate a Optimizely service and the Optimizely API cannot be reached and I call the “fetch” method the “with usecase” utility function is called with the correct usecase ID [4 ms] | |
| Error: nope | |
| at setup test/server/services/OptimizelyTest.js:308 | |
| at Context.<anonymous> test/server/services/OptimizelyTest.js:217 | |
| From console: | |
| (node:12929) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 11) | |
| test/server/services/OptimizelyTest.js [server/services/Optimizely] When I instantiate a Optimizely service and the Optimizely API cannot be reached and I call the “fetch” method the “with usecase” utility function is called with the provided logger [4 ms] | |
| Error: nope | |
| at setup test/server/services/OptimizelyTest.js:308 | |
| at Context.<anonymous> test/server/services/OptimizelyTest.js:217 | |
| From console: | |
| (node:12929) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 13) | |
| test/server/services/OptimizelyTest.js [server/services/Optimizely] When I instantiate a Optimizely service and the Optimizely API cannot be reached and I call the “fetch” method the result is a promise [5 ms] | |
| Error: nope | |
| at setup test/server/services/OptimizelyTest.js:308 | |
| at Context.<anonymous> test/server/services/OptimizelyTest.js:217 | |
| From console: | |
| (node:12929) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 7) | |
| test/server/services/OptimizelyTest.js [server/services/Optimizely] When I instantiate a Optimizely service and the Optimizely API cannot be reached and I call the “fetch” method the result is rejected [4 ms] | |
| Error: nope | |
| at setup test/server/services/OptimizelyTest.js:308 | |
| at Context.<anonymous> test/server/services/OptimizelyTest.js:217 | |
| From console: | |
| (node:12929) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 9) | |
| (node:12929) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 10) | |
| test/server/services/utils/getUsersTest.js [server/services/utils/getUsers] When I call getUsers with a client that fails the result is rejected with the error returned by my client [1 ms] | |
| Error: bax | |
| at Object.get test/server/services/utils/getUsersTest.js:32 | |
| at _callee$ src/server/services/utils/getUsers.js:11 | |
| at Context.<anonymous> test/server/services/utils/getUsersTest.js:32 | |
| From console: | |
| (node:12930) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 17) | |
| test/server/services/utils/getUsersTest.js [server/services/utils/getUsers] When I call getUsers with a client that fails the provided logger logs an error [0 ms] | |
| Error: bax | |
| at Object.get test/server/services/utils/getUsersTest.js:32 | |
| at _callee$ src/server/services/utils/getUsers.js:11 | |
| at Context.<anonymous> test/server/services/utils/getUsersTest.js:32 | |
| test/server/services/utils/getOptimizelyDataTest.js [server/services/utils/getOptimizelyData] When I call the util getOptimizelyData with an incorrect url the provided logger logs an error [2 ms] | |
| banane | |
| test/server/services/utils/getPostListTest.js [server/services/utils/getPostList] When I call getPostList with a client that fails the result is rejected with the error returned by my client [3 ms] | |
| Error: baz | |
| at Object.get test/server/services/utils/getPostListTest.js:31 | |
| at _callee$ src/server/services/utils/getPostList.js:13 | |
| at src/server/services/utils/getPostList.js:1 | |
| at Context.<anonymous> test/server/services/utils/getPostListTest.js:30 | |
| From console: | |
| (node:12930) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 13) | |
| test/server/services/utils/getOptimizelyDataTest.js [server/services/utils/getOptimizelyData] When I call the util getOptimizelyData with an incorrect url the result is a rejected promise [3 ms] | |
| banane | |
| From console: | |
| (node:12930) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 9) | |
| test/server/services/utils/withCircuitBreakerTest.js [server/services/utils/withCircuitBreaker] When I instantiate a circuit breaker factory and I call the withCircuitBreaker function six times with a function that returns a rejected promise and I call it once more the withCircuitBreaker function returns a rejected promise with the rejection message [2 ms] | |
| blablablablablabla | |
| Error: circuit breaker open | |
| at src/server/services/utils/withCircuitBreaker.js:33 | |
| at src/server/services/utils/withCircuitBreaker.js:24 | |
| at src/server/services/utils/withCircuitBreaker.js:23 | |
| at Context.<anonymous> test/server/services/utils/withCircuitBreakerTest.js:55 | |
| From console: | |
| (node:12931) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 77) | |
| test/server/services/utils/withCircuitBreakerTest.js [server/services/utils/withCircuitBreaker] When I instantiate a circuit breaker factory and I call the withCircuitBreaker function with a function that returns a rejected promise the withCircuitBreaker function returns a rejected promise with the rejection message [2 ms] | |
| bla | |
| From console: | |
| (node:12931) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 64) | |
| test/server/services/ConsulTest.js [server/services/Consul] When I create a Consul service client that connects to a healthy Consul service and I call its “start” method to start retrieving addresses from the Consul service and I wait until initialization is done and I call the “retry” method with a function that returns a rejected promise on the first and second call and a resolved promise on the second the function gets the second available address object as an argument on the second call [10 ms] | |
| Error: Consul failed to provide an IP of a healthy rumpelpumpel service | |
| at _class.retry src/server/services/Consul.js:49 | |
| at src/server/services/Consul.js:55 | |
| test/server/services/ConsulTest.js [server/services/Consul] When I create a Consul service client that connects to a healthy Consul service and I call its “start” method to start retrieving addresses from the Consul service and I wait until initialization is done and I call the “retry” method with a function that returns a rejected promise on the first and second call and a resolved promise on the second the function gets the first available address object as an argument on the first call [8 ms] | |
| Error: nopety nope | |
| at test/server/services/ConsulTest.js:345 | |
| at Context.<anonymous> test/server/services/ConsulTest.js:232 | |
| at _class.retry src/server/services/Consul.js:49 | |
| at src/server/services/Consul.js:55 | |
| at test/server/services/ConsulTest.js:345 | |
| at Context.<anonymous> test/server/services/ConsulTest.js:232 | |
| test/server/services/ConsulTest.js [server/services/Consul] When I create a Consul service client that connects to a healthy Consul service and I call its “start” method to start retrieving addresses from the Consul service and I wait until initialization is done and I call the “retry” method with a function that returns a rejected promise on the first and second call and a resolved promise on the second the function is called twice [5 ms] | |
| Error: nopety nope | |
| at test/server/services/ConsulTest.js:345 | |
| at Context.<anonymous> test/server/services/ConsulTest.js:232 | |
| Error: Consul failed to provide an IP of a healthy rumpelpumpel service | |
| at _class.retry src/server/services/Consul.js:49 | |
| at src/server/services/Consul.js:55 | |
| test/server/services/ConsulTest.js [server/services/Consul] When I create a Consul service client that connects to a healthy Consul service and I call its “start” method to start retrieving addresses from the Consul service and I wait until initialization is done and I call the “retry” method with a function that returns a rejected promise on the first call and a resolved promise on the second the result resolves with the correct value [5 ms] | |
| Error: nopety nope | |
| at test/server/services/ConsulTest.js:345 | |
| at Context.<anonymous> test/server/services/ConsulTest.js:232 | |
| test/server/services/ConsulTest.js [server/services/Consul] When I create a Consul service client that connects to a healthy Consul service and I call its “start” method to start retrieving addresses from the Consul service and I wait until initialization is done and I call the “retry” method with a function that returns a rejected promise on the first and second call and a resolved promise on the second the result is rejected with the correct error message [7 ms] | |
| Error: Consul failed to provide an IP of a healthy rumpelpumpel service | |
| at _class.retry src/server/services/Consul.js:49 | |
| at src/server/services/Consul.js:55 | |
| From console: | |
| (node:12931) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 62) | |
| test/server/services/ConsulTest.js [server/services/Consul] When I create a Consul service client that connects to a healthy Consul service and I call its “start” method to start retrieving addresses from the Consul service and I wait until initialization is done and I call the “retry” method with a function that returns a rejected promise on the first and second call and a resolved promise on the second the result is a rejected promise [10 ms] | |
| Error: nopety nope | |
| at test/server/services/ConsulTest.js:345 | |
| at Context.<anonymous> test/server/services/ConsulTest.js:232 | |
| Error: Consul failed to provide an IP of a healthy rumpelpumpel service | |
| at _class.retry src/server/services/Consul.js:49 | |
| at src/server/services/Consul.js:55 | |
| Error: nopety nope | |
| at test/server/services/ConsulTest.js:345 | |
| at Context.<anonymous> test/server/services/ConsulTest.js:232 | |
| From console: | |
| (node:12931) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 57) | |
| test/server/services/ConsulTest.js [server/services/Consul] When I create a Consul service client that connects to a healthy Consul service and I call its “start” method to start retrieving addresses from the Consul service and I wait until initialization is done and I call the “retry” method with a function that returns a resolved promise the result resolves with the correct value [8 ms] | |
| Error: nopety nope | |
| at test/server/services/ConsulTest.js:345 | |
| at Context.<anonymous> test/server/services/ConsulTest.js:232 | |
| test/server/services/ConsulTest.js [server/services/Consul] When I create a Consul service client that connects to a healthy Consul service and I call its “start” method to start retrieving addresses from the Consul service and I wait until initialization is done and I call the “retry” method with a function that returns a resolved promise the result is a resolved promise [6 ms] | |
| Error: nopety nope | |
| at test/server/services/ConsulTest.js:345 | |
| at Context.<anonymous> test/server/services/ConsulTest.js:232 | |
| test/server/services/ConsulTest.js [server/services/Consul] When I create a Consul service client that connects to a healthy Consul service and I call its “start” method to start retrieving addresses from the Consul service and I wait until initialization is done and I call the “retry” method with a function that returns a resolved promise the function gets called with the first available address object [4 ms] | |
| Error: nopety nope | |
| at test/server/services/ConsulTest.js:345 | |
| at Context.<anonymous> test/server/services/ConsulTest.js:232 | |
| test/server/services/ConsulTest.js [server/services/Consul] When I create a Consul service client that connects to a healthy Consul service and I call its “start” method to start retrieving addresses from the Consul service and I wait until initialization is done and I call the “retry” method with a function that returns a resolved promise the function is called once [4 ms] | |
| Error: nopety nope | |
| at test/server/services/ConsulTest.js:345 | |
| at Context.<anonymous> test/server/services/ConsulTest.js:232 | |
| test/server/services/ConsulTest.js [server/services/Consul] When I create a Consul service client that connects to a healthy Consul service and I call its “start” method to start retrieving addresses from the Consul service and I wait until initialization is done and I call the “retry” method with a function that returns a rejected promise on the first call and a resolved promise on the second the result is a resolved promise [7 ms] | |
| Error: nopety nope | |
| at test/server/services/ConsulTest.js:345 | |
| at Context.<anonymous> test/server/services/ConsulTest.js:232 | |
| test/server/services/ConsulTest.js [server/services/Consul] When I create a Consul service client that connects to a healthy Consul service and I call its “start” method to start retrieving addresses from the Consul service and I wait until initialization is done and I call the “retry” method with a function that returns a rejected promise on the first call and a resolved promise on the second the function gets the second available address object as an argument on the second call [7 ms] | |
| Error: nopety nope | |
| at test/server/services/ConsulTest.js:345 | |
| at Context.<anonymous> test/server/services/ConsulTest.js:232 | |
| test/server/services/ConsulTest.js [server/services/Consul] When I create a Consul service client that connects to a healthy Consul service and I call its “start” method to start retrieving addresses from the Consul service and I wait until initialization is done and I call the “retry” method with a function that returns a rejected promise on the first call and a resolved promise on the second the function gets the first available address object as an argument on the first call [6 ms] | |
| Error: nopety nope | |
| at test/server/services/ConsulTest.js:345 | |
| at Context.<anonymous> test/server/services/ConsulTest.js:232 | |
| test/server/services/ConsulTest.js [server/services/Consul] When I create a Consul service client that connects to a healthy Consul service and I call its “start” method to start retrieving addresses from the Consul service and I wait until initialization is done and I call the “retry” method with a function that returns a rejected promise on the first call and a resolved promise on the second the function is called twice [6 ms] | |
| Error: nopety nope | |
| at test/server/services/ConsulTest.js:345 | |
| at Context.<anonymous> test/server/services/ConsulTest.js:232 | |
| test/server/services/ConsulTest.js [server/services/Consul] When I create a Consul service client that connects to a healthy Consul service where services are running on the same node and I call its “start” method to start retrieving addresses from the Consul service and I wait until initialization is done and I call the “next” method the result has a “port” property [4 ms] | |
| Error: nopety nope | |
| at test/server/services/ConsulTest.js:345 | |
| at Context.<anonymous> test/server/services/ConsulTest.js:147 | |
| test/server/services/ConsulTest.js [server/services/Consul] When I create a Consul service client that connects to a healthy Consul service where services are running on the same node and I call its “start” method to start retrieving addresses from the Consul service and I wait until initialization is done and I call the “next” method the result has an “address” property [4 ms] | |
| Error: nopety nope | |
| at test/server/services/ConsulTest.js:345 | |
| at Context.<anonymous> test/server/services/ConsulTest.js:147 | |
| test/server/services/ConsulTest.js [server/services/Consul] When I create a Consul service client that connects to a healthy Consul service and I call its “start” method to start retrieving addresses from the Consul service and I wait until initialization is done and I call the “stop” method and I wait until the consul client's update interval has passed and I call the “next” method the result is still null [4 ms] | |
| Error: nopety nope | |
| at test/server/services/ConsulTest.js:345 | |
| at Context.<anonymous> test/server/services/ConsulTest.js:43 | |
| test/server/services/ConsulTest.js [server/services/Consul] When I create a Consul service client that connects to a Consul service that breaks after a while and I call its “start” method to start retrieving addresses from the Consul service and I wait until initialization is done and I call the “next” method and I wait until the consul client's update interval has passed and I call the “next” method the result is null [5 ms] | |
| Error: nopety nope | |
| at test/server/services/ConsulTest.js:345 | |
| at Context.<anonymous> test/server/services/ConsulTest.js:200 | |
| From console: | |
| (node:12931) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 23) | |
| test/server/services/ConsulTest.js [server/services/Consul] When I create a Consul service client that connects to a Consul service that breaks after a while and I call its “start” method to start retrieving addresses from the Consul service and I wait until initialization is done and I call the “next” method the result has a “port” property [4 ms] | |
| Error: nopety nope | |
| at test/server/services/ConsulTest.js:345 | |
| at Context.<anonymous> test/server/services/ConsulTest.js:200 | |
| test/server/services/ConsulTest.js [server/services/Consul] When I create a Consul service client that connects to a Consul service that breaks after a while and I call its “start” method to start retrieving addresses from the Consul service and I wait until initialization is done and I call the “next” method the result has an “address” property [4 ms] | |
| Error: nopety nope | |
| at test/server/services/ConsulTest.js:345 | |
| at Context.<anonymous> test/server/services/ConsulTest.js:200 | |
| test/server/services/ConsulTest.js [server/services/Consul] When I create a Consul service client that connects to a healthy Consul service and I call its “start” method to start retrieving addresses from the Consul service and I wait until initialization is done and I call the “next” method and I call the “next” method again and I call the “next” method a third time and I call the consul clients “remove” method with the current result (IP ending with 209) and I call the “next” method the result has a “port” property [4 ms] | |
| Error: nopety nope | |
| at test/server/services/ConsulTest.js:345 | |
| at Context.<anonymous> test/server/services/ConsulTest.js:43 | |
| test/server/services/ConsulTest.js [server/services/Consul] When I create a Consul service client that connects to a healthy Consul service and I call its “start” method to start retrieving addresses from the Consul service and I wait until initialization is done and I call the “next” method and I call the “next” method again and I call the “next” method a third time and I call the consul clients “remove” method with the current result (IP ending with 209) and I call the “next” method the result has the IP address ending with 210 [4 ms] | |
| Error: nopety nope | |
| at test/server/services/ConsulTest.js:345 | |
| at Context.<anonymous> test/server/services/ConsulTest.js:43 | |
| at test/server/services/ConsulTest.js:345 | |
| at test/server/services/ConsulTest.js:43 | |
| test/server/services/ConsulTest.js [server/services/Consul] When I create a Consul service client that connects to a healthy Consul service and I call its “start” method to start retrieving addresses from the Consul service and I wait until initialization is done and I call the “stop” method and I call the “next” method the result is null [5 ms] | |
| Error: nopety nope | |
| at test/server/services/ConsulTest.js:345 | |
| at Context.<anonymous> test/server/services/ConsulTest.js:43 | |
| test/server/services/ConsulTest.js [server/services/Consul] When I create a Consul service client that connects to a healthy Consul service and I call its “start” method to start retrieving addresses from the Consul service and I wait until initialization is done and I call the “next” method and I call the “next” method again and I call the “next” method a third time and I call the consul clients “remove” method with the current result (IP ending with 209) and I call the “next” method and I call the “next” method and I call the “remove” method with the current result (IP ending with 210) and I call the “next” method and I wait until the consul client has loaded a fresh set of IP addresses and I call the “next” method the result has a “port” property [4 ms] | |
| Error: nopety nope | |
| at test/server/services/ConsulTest.js:345 | |
| at Context.<anonymous> test/server/services/ConsulTest.js:43 | |
| test/server/services/ConsulTest.js [server/services/Consul] When I create a Consul service client that connects to a healthy Consul service and I call its “start” method to start retrieving addresses from the Consul service and I wait until initialization is done and I call the “next” method and I call the “next” method again and I call the “next” method a third time and I call the consul clients “remove” method with the current result (IP ending with 209) and I call the “next” method and I call the “next” method and I call the “remove” method with the current result (IP ending with 210) and I call the “next” method and I wait until the consul client has loaded a fresh set of IP addresses and I call the “next” method the result has an “address” property [6 ms] | |
| Error: nopety nope | |
| at test/server/services/ConsulTest.js:345 | |
| at Context.<anonymous> test/server/services/ConsulTest.js:43 | |
| test/server/services/ConsulTest.js [server/services/Consul] When I create a Consul service client that connects to a healthy Consul service and I call its “start” method to start retrieving addresses from the Consul service and I wait until initialization is done and I call the “next” method and I call the “next” method again and I call the “next” method a third time and I call the consul clients “remove” method with the current result (IP ending with 209) and I call the “next” method and I call the “next” method and I call the “remove” method with the current result (IP ending with 210) and I call the “next” method the result is null [3 ms] | |
| Error: nopety nope | |
| at test/server/services/ConsulTest.js:345 | |
| at Context.<anonymous> test/server/services/ConsulTest.js:43 | |
| test/server/services/ConsulTest.js [server/services/Consul] When I create a Consul service client that connects to a healthy Consul service and I call its “start” method to start retrieving addresses from the Consul service and I wait until initialization is done and I call the “next” method the result has a “port” property [5 ms] | |
| Error: nopety nope | |
| at test/server/services/ConsulTest.js:345 | |
| at Context.<anonymous> test/server/services/ConsulTest.js:43 | |
| test/server/services/ConsulTest.js [server/services/Consul] When I create a Consul service client that connects to a healthy Consul service and I call its “start” method to start retrieving addresses from the Consul service and I wait until initialization is done and I call the “next” method the result has an “address” property [8 ms] | |
| Error: nopety nope | |
| at test/server/services/ConsulTest.js:345 | |
| at Context.<anonymous> test/server/services/ConsulTest.js:43 | |
| test/server/services/ConsulTest.js [server/services/Consul] When I create a Consul service client that connects to a healthy Consul service and I call its “start” method to start retrieving addresses from the Consul service and I wait until initialization is done and I call the “next” method and I call the “next” method again and I call the “next” method a third time the result has a “port” property [5 ms] | |
| Error: nopety nope | |
| at test/server/services/ConsulTest.js:345 | |
| at Context.<anonymous> test/server/services/ConsulTest.js:43 | |
| test/server/services/ConsulTest.js [server/services/Consul] When I create a Consul service client that connects to a healthy Consul service and I call its “start” method to start retrieving addresses from the Consul service and I wait until initialization is done and I call the “next” method and I call the “next” method again and I call the “next” method a third time the result has the first address again [4 ms] | |
| Error: nopety nope | |
| at test/server/services/ConsulTest.js:345 | |
| at Context.<anonymous> test/server/services/ConsulTest.js:43 | |
| test/server/services/ConsulTest.js [server/services/Consul] When I create a Consul service client that connects to a healthy Consul service and I call its “start” method to start retrieving addresses from the Consul service and I wait until initialization is done and I call the “next” method and I call the “next” method again the result has a “port” property [4 ms] | |
| Error: nopety nope | |
| at test/server/services/ConsulTest.js:345 | |
| at Context.<anonymous> test/server/services/ConsulTest.js:43 | |
| test/server/services/ConsulTest.js [server/services/Consul] When I create a Consul service client that connects to a healthy Consul service and I call its “start” method to start retrieving addresses from the Consul service and I wait until initialization is done and I call the “next” method and I call the “next” method again the result has the next address [19 ms] | |
| Error: nopety nope | |
| at test/server/services/ConsulTest.js:345 | |
| at Context.<anonymous> test/server/services/ConsulTest.js:43 | |
| test/server/services/utils/validateAccessTokenTest.js [server/utils/validateAccessToken] When I call “validate access token” and an error is thrown while trying to access the service an error is thrown [2 ms] | |
| Error: WTF!?! | |
| at Object.get test/server/services/utils/validateAccessTokenTest.js:48 | |
| at _callee$ src/server/services/utils/validateAccessToken.js:30 | |
| at src/server/services/utils/validateAccessToken.js:1 | |
| at Context.<anonymous> test/server/services/utils/validateAccessTokenTest.js:47 | |
| From console: | |
| (node:12932) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 11) | |
| test/server/services/utils/validateAccessTokenTest.js [server/utils/validateAccessToken] When I call “validate access token” and an error is thrown while trying to access the service the provided logger logs an error [2 ms] | |
| Error: WTF!?! | |
| at Object.get test/server/services/utils/validateAccessTokenTest.js:48 | |
| at _callee$ src/server/services/utils/validateAccessToken.js:30 | |
| at src/server/services/utils/validateAccessToken.js:1 | |
| at Context.<anonymous> test/server/services/utils/validateAccessTokenTest.js:47 | |
| test/server/services/utils/getThreadInfoTest.js [server/services/utils/getThreadInfo] When I call getThreadInfo with a client that fails the provided logger logs an error [1 ms] | |
| Error: bar | |
| at Object.get test/server/services/utils/getThreadInfoTest.js:37 | |
| at _callee$ src/server/services/utils/getThreadInfo.js:13 | |
| at src/server/services/utils/getThreadInfo.js:1 | |
| at Context.<anonymous> test/server/services/utils/getThreadInfoTest.js:36 | |
| test/server/services/utils/getThreadInfoTest.js [server/services/utils/getThreadInfo] When I call getThreadInfo with a client that fails the result is rejected with the error returned by my client [2 ms] | |
| Error: bar | |
| at Object.get test/server/services/utils/getThreadInfoTest.js:37 | |
| at _callee$ src/server/services/utils/getThreadInfo.js:13 | |
| at src/server/services/utils/getThreadInfo.js:1 | |
| at Context.<anonymous> test/server/services/utils/getThreadInfoTest.js:36 | |
| From console: | |
| (node:12932) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 6) | |
| test/server/services/utils/getBoardsTest.js [server/services/utils/getPostList] When I call getPostList with a client that fails the result is rejected with the error returned by my client [7 ms] | |
| Error: baz | |
| at Object.get test/server/services/utils/getBoardsTest.js:26 | |
| at _callee$ src/server/services/utils/getBoards.js:10 | |
| at src/server/services/utils/getBoards.js:1 | |
| at Context.<anonymous> test/server/services/utils/getBoardsTest.js:25 | |
| From console: | |
| (node:12932) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 2) | |
| test/server/services/utils/getBoardsTest.js [server/services/utils/getPostList] When I call getPostList with a client that fails the provided logger logs an error [2 ms] | |
| Error: baz | |
| at Object.get test/server/services/utils/getBoardsTest.js:26 | |
| at _callee$ src/server/services/utils/getBoards.js:10 | |
| at src/server/services/utils/getBoards.js:1 | |
| at Context.<anonymous> test/server/services/utils/getBoardsTest.js:25 | |
| test/server/services/MotorTalkTest.js [server/services/MotorTalk] When I instantiate a MotorTalk API client with proxy config and a call to get boards that fails and I call the getBoards method the result is a promise rejected with the error from get thread info [40 ms] | |
| nagnag | |
| nagnag | |
| From console: | |
| (node:12934) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 19) | |
| (node:12934) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 20) | |
| test/server/services/MotorTalkTest.js [server/services/MotorTalk] When I instantiate a MotorTalk API client with proxy config and a call to get boards that fails and I call the getBoards method the provided logger logs an error [27 ms] | |
| nagnag | |
| nagnag | |
| From console: | |
| (node:12934) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 21) | |
| test/server/services/MotorTalkTest.js [server/services/MotorTalk] When I instantiate a MotorTalk API client with proxy config and a call to get users that fails and I call the getPostList method the result is a promise rejected with the error from get thread info [44 ms] | |
| rapante | |
| rapante | |
| From console: | |
| (node:12934) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 15) | |
| (node:12934) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 16) | |
| test/server/services/MotorTalkTest.js [server/services/MotorTalk] When I instantiate a MotorTalk API client with proxy config and a call to get users that fails and I call the getPostList method the provided logger logs an error [40 ms] | |
| rapante | |
| rapante | |
| From console: | |
| (node:12934) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 17) | |
| test/server/services/MotorTalkTest.js [server/services/MotorTalk] When I instantiate a MotorTalk API client with proxy config and a call to get post list that fails and I call the getPostList method the result is a promised rejected with the error from get thread info [59 ms] | |
| corge | |
| corge | |
| From console: | |
| (node:12934) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 11) | |
| (node:12934) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 12) | |
| test/server/services/MotorTalkTest.js [server/services/MotorTalk] When I instantiate a MotorTalk API client with proxy config and a call to get post list that fails and I call the getPostList method the provided logger logs an error [42 ms] | |
| corge | |
| corge | |
| From console: | |
| (node:12934) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 13) | |
| test/server/services/MotorTalkTest.js [server/services/MotorTalk] When I instantiate a MotorTalk API client with proxy config and a call to request access token validation that that fails and I call the validateAccessToken method the provided logger logs an error [42 ms] | |
| Nope, I will not validate your stupid token! | |
| Nope, I will not validate your stupid token! | |
| From console: | |
| (node:12934) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 8) | |
| test/server/services/MotorTalkTest.js [server/services/MotorTalk] When I instantiate a MotorTalk API client with proxy config and a call to get thread info that fails and I call the getPostList method the result is a promised rejected with the error from get thread info [52 ms] | |
| graultgrault | |
| From console: | |
| (node:12934) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 1) | |
| (node:12934) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 2) | |
| test/server/services/MotorTalkTest.js [server/services/MotorTalk] When I instantiate a MotorTalk API client with proxy config and a call to get thread info that fails and I call the getPostList method the provided logger logs an error [50 ms] | |
| grault | |
| grault | |
| Nope, I will not validate your stupid token! | |
| Nope, I will not validate your stupid token! | |
| From console: | |
| (node:12934) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 3) | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment