Introducing Sveste
33 |34 | Anyone can write a unit test. But a great unit test? 35 |
36 |37 | Great unit tests focus on what a user should see and do, 38 | not the implementation details. They fail when you break your UX. They don’t break when you 41 | refactor your code. 42 |
43 | 44 |45 | Great unit tests help you focus on your users, not yourself. 46 |
47 | 48 |But this introduces a contradiction.
49 | 50 |51 | Your sales and service reps talk to users every day. They understand 52 | how people want to use your product, but don’t have the technical 53 | skills to turn that knowledge into tests. Your engineers know how to 54 | code, but don’t have the time to get on the phone with hundreds of 55 | people a day. 56 |
57 | 58 |59 | The people that understand your users can’t write tests. And the 60 | people that write tests don’t understand your users. So what do you 61 | do? 62 |
63 | 64 |You sit in meetings and hope for the best.
65 | 66 |But what if there was a better way?
67 | 68 |Enter Sveste: a no-code GUI for writing great unit tests.
69 | 70 |71 | Today, Sveste (Svelte + test) translates form inputs into executable 72 | tests. It uses the 73 | Testing Library to focus on 74 | best practices like testing what’s actually on screen. It uses 75 | Vitest so you can take advantage of 76 | Vite’s fast build times and run unit tests as you code. It structures 77 | your code so that each unit test is (human) readable and independent ( 78 | no nested mock statements here 81 | ). Sveste ensures that your test code is concise, functional, and best 82 | practice. 83 |
84 | 85 |86 | But this is just a first step to a bigger goal (literally, it’s 87 | v0.2!). 88 |
89 | 90 |We want Sveste to help you write tests in plain English.
91 | 92 |93 | Imagine if writing tests were as easy as Mad Libs? Imagine if you got 94 | context-aware tips as you wrote your tests: guiding you towards 95 | helpful resources, and steering you away from common testing mistakes? 96 | Imagine if you could share unit tests with others, and build off of 97 | each-other’s work to write application agnostic tests? 98 |
99 | 100 |Help us make this vision a reality!
101 | 102 |103 | Sveste is open source, and looking for contributors. Check out our 104 | app and 105 | repo to get 106 | started! 107 |
108 |
18 |
65 |
68 |
96 |