Hi HN, we have been building this open source tool to make creating browser tests easier. It converts your browser actions to Playwright/Jest code and sets up CI with one command. We would love any feedback!
I have had the same experience using Selenium but not with Chrome Dev Tools Protocol. However you still need a stable environment, trustable selectors, and automatic waiting logic to have stable e2e web tests.
I am working on an open source library that generates Playwright tests (uses Chrome Dev Tools protocol) and I hope we can prove you wrong about getting UI tests working reliably. https://github.com/qawolf/qawolf
We work with large health insurance companies in the US to lower the cost of drugs for their patients and make it easy for them to receive, manage, and adhere to their prescriptions.
We need your help to expand our platform to more patients and to play a part in fixing a massive and very broken segment of the healthcare industry. We are a small and tight-knit engineering team of two and are looking for a third to share our many hats, including:
- Frontend development with react / react native / redux
- Backend development with node / graphql / postgres
- Data analysis of patient records with python / pandas / tensorflow
We're looking for another self-starter who can design and build architecturally-sound foundations to last, and who has the track record to prove it. We're engineers that care about what we're building and take an active role in the product design process.
Joins are a really hard problem, many people have tried to support joins with a package but they all miss a corner case or have less-than-ideal performance. I think it is something we will have to wait for meteor core to support. https://trello.com/c/BGvIwkEa/48-easy-joins-in-subscriptions
In the meantime I have been using the publish-composite package and denormalizing data that has a lot of reads in an update hook using the collection hooks package.
In mongo ideally you should have rich documents and not spread out relations among too many collections. However I can imagine how hard it would be to try and sync w/ a relational database without native join support.
I have built and integrated some pretty complex components with blaze templates without needing a component api. I am curious what use case you ran into where the template api was not sufficient?
In your comment history I saw that you asked for reactive template variables. I know of two ways to accomplish that, 1) attach a ReactiveDict to a template instance in it's render function, 2) pass it in as a variable to the template inclusion {{>template myDict}}.
What is nice about meteor is how quickly you can get off the ground and build something with it. Then you realize: I have no idea how this stuff works. Is it secure? When do things update? Is there too much magic?
But if you spend a bit of time learning how meteor’s core packages work (deps, ddp, livedata, blaze, etc) and how they work together — almost all of the apprehension disappears.
I recommend digging into the Deps package first, it powers reactivity and is surprisingly simple (only 1 kb).
Meteor also started putting together a manual to explain the core concepts http://manual.meteor.com — the first chapter is about the Deps package.
With any new concept there is a learning curve. But I believe the concepts meteor introduce are too powerful to ignore. The saying is that any sufficiently advanced technology is indistinguishable from magic :)
I saw the link in the meteor tech talk but figured it was not for public distribution. However now that it is in the wild, for the curious I have been de-minifying the paper example to try and learn how to use famo.us.
Also I am not sure why there are all these haters. In the few days I have been using it, I can see it is going to change mobile web app development entirely. Really excited for the launch!