SafeTest: A novel approach to front end testing
netflixtechblog.com
SafeTest: A novel approach to front end testing
1–10 of 35 posts
Re: SafeTest: A novel approach to front end testing
#2Not sure why this is fundamentally different from existing e2e testers with bootstrapping
Re: SafeTest: A novel approach to front end testing
#3My initial impression of this is that it enables controlling just how much of the app you want to render for your test, while more traditional solutions force you towards either rendering the whole app or testing just a component. Is that accurate?
Re: SafeTest: A novel approach to front end testing
#4My initial impression of this is that it enables controlling just how much of the app you want to render for your test, while more traditional solutions force you towards either rendering the whole app or testing just a component. Is that accurate?
Yes, that's correct. You get all the benefits of react-testing-library mounting and the ability to test the entire app as a unit.
Re: SafeTest: A novel approach to front end testing
#5Not sure why this is fundamentally different from existing e2e testers with bootstrapping
Can you clarify what you mean? Usually, e2e testers don't have a bootstrapping stage for app-level changes, only for things that can be done via the browser automation APIs.
Re: SafeTest: A novel approach to front end testing
#6how many billions of dollars and they still host their blog on a nagware site SMH It's not like moving would be high drama since they already have a custom domain for it
https://scribe.rip/introducing-safetest-a-novel-approach-to-...
Re: SafeTest: A novel approach to front end testing
#7how many billions of dollars and they still host their blog on a nagware site SMH It's not like moving would be high drama since they already have a custom domain for it https://scribe.rip/introducing-safetest-a-novel-approach-to-...
it also has no license file, with https://github.com/kolodny/safetest/blob/main/package.json#L... saying "MIT" but as far as I know it says that a lot and I doubt gravely that any court would consider a json file a legitimate license declaration
Re: SafeTest: A novel approach to front end testing
#8how many billions of dollars and they still host their blog on a nagware site SMH It's not like moving would be high drama since they already have a custom domain for it https://scribe.rip/introducing-safetest-a-novel-approach-to-...
it also has no license file, with https://github.com/kolodny/safetest/blob/main/package.json#L... saying "MIT" but as far as I know it says that a lot and I doubt gravely that any court would consider a json file a legitimate license declaration
Sorry about that. I just added an official LICENSE file
Re: SafeTest: A novel approach to front end testing
#9how many billions of dollars and they still host their blog on a nagware site SMH It's not like moving would be high drama since they already have a custom domain for it https://scribe.rip/introducing-safetest-a-novel-approach-to-...
Is hitting the (x) on the banner that difficult?
Re: SafeTest: A novel approach to front end testing
#10how many billions of dollars and they still host their blog on a nagware site SMH It's not like moving would be high drama since they already have a custom domain for it https://scribe.rip/introducing-safetest-a-novel-approach-to-...
Is hitting the (x) on the banner that difficult?
Is having nagware for another company a good look for an engineering blog?
> How we GraphQL all the things, after this brief message from our ... sponsor?