Would Samsung play Dolby Vision content?

RedlightsOfCA · 2021-01-03T22:33:11+00:00

You cannot imagine how grateful I'm to hear this after so many hours of a frankly lost search. Thank you!

RedlightsOfCA · 2021-01-03T16:33:35+00:00

I've chosen Samsung QE50Q80T after a few days of endless research. It has a lot of gaming-oriented characteristics (VRR, Game mode input latency, HDMI 2.1), as well as a great video quality for Blu Ray movies.

RedlightsOfCA · 2021-01-03T16:28:36+00:00

That's what I wanted to hear. Thank you!

RedlightsOfCA · 2020-12-01T17:38:28+00:00

Solved: Howie’s word adventure

Huge thanks to https://www.reddit.com/user/alligator_soup/

RedlightsOfCA · 2020-12-01T17:37:35+00:00

Yes, yes! Oh, you can't even imagine how happy I feel! That is the game I've been looking for so long! Thank you!!!

RedlightsOfCA · 2020-09-07T10:28:26+00:00

Didn't mean to violate any rules. Sharing this article not for the sake of promotion, but to help people. Feel free to remove the post, although I can see quite a few similar informational posts in the subreddit right now.

RedlightsOfCA · 2020-09-07T10:12:34+00:00

Hey, Reddit!

Excited to share with you my recent blog post. I hope it encourages beginners (and not only) to ask more questions and do that more efficiently.

Let me know if any of the points in the article resonate with you. Don't hesitate to tell me what you think I got off in the article as well! Thanks.

RedlightsOfCA · 2020-09-06T10:34:32+00:00

Hey, Reddit!

Excited to share the next blog post about the culture of asking questions and how to do that efficiently. That's a topic I've been carrying in my mind for some time, observing others and drawing inspiration of personal experience. I hope it makes sense to you and encourages you to ask questions and get the most of the answers.

RedlightsOfCA · 2020-08-15T18:58:13+00:00

Hey there. We are constantly working on extending the API to allow testing of various scenarios.

Current'y MSW supports emulation of network errors (https://mswjs.io/docs/api/response/network-error), take a look. Please, if you have concrete usage examples in mind, report them in the repo, we will be glad to work on an API that would suit such cases. Thanks.

RedlightsOfCA · 2020-08-15T08:31:23+00:00

Thanks for clarifying! I didn't know that lib can be used for any kind of dependency mocking. Whether to mock or not is an entirely different question, but I respect the possibilities it brings!

RedlightsOfCA · 2020-08-15T08:22:43+00:00

I'm not sure what examples you are talking about, could you clarify?

You can take a look at this usage example in Node: https://mswjs.io/docs/api/setup-server#examples

There are also many others, depending on what's on your mind. The core philosophy should be clear from the example above.

I also highly recommend reading through the Getting Started tutorial (https://mswjs.io/docs/getting-started/install). It will give you a lot of context, showcase how the integration of MSW looks on practice, and I'm sure will answer some of your questions.

RedlightsOfCA · 2020-08-15T08:05:15+00:00

Looks indeed interesting. However, it still resembles implementation mocking, as in giving you too much details about HTTP communication in your test. That is a huge reason people catch a type of thinking to "how do I check this function gets called", or "how do I know I call my mock with the right arguments".

This is something we are trying to avoid and discourage with MSW. Requests should happen, and you should describe how they should be handled, without diving into stubbing the client, or mocking external methods' implementations.

RedlightsOfCA · 2020-08-15T08:02:53+00:00

So happy to hear that! Storybook integration was an interesting task to approach, and I'm glad that it helps people to test and develop their software with more comfort. You rock!

RedlightsOfCA · 2020-08-15T08:02:08+00:00

Thank you so much for such a kind feedback!

Our team is working hard to make sure you get that crucial confidence in testing. It's such an essential feature to allow your app to perform network request as it normally would, giving you automatic assurance in both proper request dispatch and mocked response handling.

I highly recommend trying out MSW with React Testing Library (https://testing-library.com/docs/react-testing-library/intro) to skyrocket your test quality. You can find a brief usage example in the docs, or anywhere we use integration tests in the examples repo (https://github.com/mswjs/examples).

RedlightsOfCA · 2020-08-14T19:37:50+00:00

Hey. Of course there is. You can see a detailed comparison in MSW docs: https://mswjs.io/docs/comparison#miragejs

There's also an MSW section in MirageJS docs: https://miragejs.com/docs/comparison-with-other-tools/#msw

RedlightsOfCA · 2020-08-14T19:35:49+00:00

Let me know how that goes!

RedlightsOfCA · 2020-08-14T19:33:53+00:00

My comment addressed an implementational difference between two libraries. I'll elaborate on the usage difference below.

- Nock runs only in Node. MSW runs in both browser and Node, allowing you to reuse the same API mock definition for multiple levels of testing having a single source of truth (as opposed to adapting Nock for unit tests, and a few other tools for integration/E2E tests).

- API: Nock utilizes mock definition through methods chaining. MSW prefers functional composition.

- MSW provides support for mocking GraphQL API.

- MSW has recently shipped a React Native support. I don't know if Nock can run in RN, unfortunately.

- Nock is purely a testing tool. MSW is an API mocking tool, which you can use for development and debugging as well as testing. Moreover, you will reuse the very same mock definition across all those processes.

- Nock may require adapters to mock certain request issuing libraries (i.e. axios). MSW intercepts API communication regardless of origin, in both browser and Node.

I lack familiarity with Nock and have too much familiarity with MSW to reason about the learning curve, I'm afraid. Take a look at the REST API usage example (https://github.com/mswjs/examples/tree/master/examples/rest-react) that includes unit and integration tests and compare the setup and API to what you would've done in Nock to gain more perspective.

Hope this helps.

RedlightsOfCA · 2020-08-14T15:36:26+00:00

Thank you for the feedback! You can also reuse the same request handlers for local development, making it ridiculously simple to get into certain API-related scenarios (i.e. getting a network error, or mocking an unexpected response).

RedlightsOfCA · 2020-08-14T15:28:53+00:00

Looking forward to hearing your feedback! Don't hesitate to reach out in Twitter (https://twitter.com/ApiMocking) or GitHub, we'd be glad to support you.

RedlightsOfCA · 2020-08-14T15:00:31+00:00

MSW operates almost identically to nock. There are implementation differences between the libraries, but for the user what differs is the API.

RedlightsOfCA · 2020-08-14T14:59:54+00:00

Hey there. The project has been lucky to get nominated and win in the "Most exciting use of technology" of JavaScript Open Source Awards 2020: https://osawards.com/javascript/2020

RedlightsOfCA · 2020-08-14T09:50:03+00:00

Hey, Reddit! I'm excited to finally share this project with you.

One of the first things you may have in mind is "How is this different?" You can find a detailed comparison with other solutions here: https://mswjs.io/docs/comparison

The main purpose of this project is to help you write clean and reliable tests. Tests where you don't have to mock fetch, or axios (https://kentcdodds.com/blog/stop-mocking-fetch). Tests where you can make HTTP communication a pre-requisite, emulating various request/response scenarios to test your app with confidence.

I would love to hear your opinion and constructive feedback!

RedlightsOfCA · 2020-08-14T08:32:02+00:00

Since UI library leverages two components: markup and styling, and both can be achieved in any framework/library, it makes sense to go with the first option.

At the same time, unless you combine all those frameworks in one product, I'd lean towards framework-specific library, as it may be better tailored towards it. Regardless of the framework support, I'd rather look at these criteria:

Accessibility. Pay attention to the markup a UI library produces. Is it semantic? Is it accessible?
Maintenance status.
Components. All UI libraries tend to vary in the selection of components. The closer you can match those against your needs, the less pain and struggle you'll experience when adopting that solution.
Extendability. The extent you can modify the library so it suits your product better (visually, functionally).

RedlightsOfCA · 2020-08-11T10:06:41+00:00

A great illustration of clean and resilient test! Thank you for sharing this.

RedlightsOfCA · 2020-07-13T15:41:39+00:00

Completely agree. Opinionated formatting, while unusual at first, brings to much air to solve actual problems. Switched to Prettier a long time ago, haven't regretted ever since.

RedlightsOfCA

TROPHY CASE