Show HN: Git push to start a build
debuggie.com3 pointsby ksks0 comments
Who is your market with this?
That is a very good question. My original intend is for developers. Although there are tools like selenium, setting up, writing and running automated tests can still take a lot of time for the developers. Thats why I believe most developers still do some levels of manual testing, either during developing a feature or after, because the cost of automating it is too high (can easily exceed the time to develop the feature being tested). My frontend developer friends find my app useful mainly because it allows them to validate their code, even in the middle of development where the code churn is very high, since creating and running the tests are almost effortless. Plus, I could add the feature to export the tests/scenarios into test code, which would also be a huge time saver for developers, but this could take weeks.
For example, if you have a <form> with a text field (input[type=text]) and a submit button, if you hit 'Enter' in the text field, you get a submit event, nothing surprising. But did you know you also get an artificial click event on the submit button, before the submit event?
Now what if you don't have the submit button? Then hitting the 'Enter' key would still generate a submit event, but without any artificial click event now.
OK, what if you want to have two textfields now (and still no submit button)? Then hitting 'Enter' would...you guessed it, NOT generate any submit events. No submit event, no artificial click, not even moving the focus from one text field to the other.
But what if you have a non text base input (color, date, range, etc) and hit 'Enter' on it? Yes, you get a submit event, but ONLY if you have a submit button. Otherwise no, even if you have just a single non-text based input.
And all these are just for Chrome. Other browsers behave somewhat differently.