Launching today
Evaficy Smart Test
AI-generated test cases from your acceptance criteria
7 followers
AI-generated test cases from your acceptance criteria
7 followers
Manage QA projects, generate test cases with AI, validate with expert workflows, and run structured test executions with pass/fail tracking — all in one platform.
@andrei_constantin_alexandru Hi, Andrei! As a solo dev, I'd say testing my own projects can definitely be a bit chaotic, so adding more structure is a great idea and I like that the tool tries to educate me about test cases in the first place (I found the articles at the bottom of the page). Maybe there is a way to make the content easier to find and read, such as adding links in the form, using more visuals (graphs), or making the font bigger. Overall, I was able to log in and use the tool, but please check the Google sign-in because it currently gives me a 500 error.
@theicreator Hi Serhii, thank you for taking the time to actually test Evaficy Smart Test and share such detailed feedback, this is exactly the kind of input that helps shape the product.
Really glad the articles at the bottom resonated with you, making QA knowledge more accessible alongside the tool is something I care about. Your point about discoverability is valid, adding contextual links directly in the form is a great idea I'll take note of.
Regarding the Google sign-in 500 error, I just tested it and it's working on my end at least for Log in, but I'd love to investigate your specific case further. Could you please share which browser and OS you were on? It's possible there's an edge case I need to track down.
Thanks again for the thoughtful feedback and for upvoting, really appreciated on launch day!
@andrei_constantin_alexandru I tried on a different account and can say now the sign up is the issue, not the sign in. I see nothing unusual in the network tab, probably server logs could tell more? Tested on Mac OS, Arc browser. This is the redirect url after google consent screen: ```https://app.evaficy.com/auth/google/callback?iss=https%3A%2F%2Faccounts.google.com&code=4%2F0AdkVLPwutJu20kuhOkKTscFhStAB1_sM3WU2kEgjgKCgBrKv6V5wuNasn2fWDwUQJSB-Ng&scope=email+profile+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.email+openid+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.profile&authuser=2&prompt=none```
@theicreator Thank you for the detailed investigation — this is really helpful. The authuser=2 parameter in the callback URL suggests you were using a third Google account in your browser, which is likely the edge case causing the 500 error. I'll investigate the callback handler's behavior with multiple Google sessions. Really appreciate you digging into the network tab and sharing the redirect URL.
Generated a full suite of test cases from a single paragraph of requirements, which saved me at least an hour of writing. The expert validation step caught a couple of edge cases I would have definitely missed.
Test case generation saved me a ton of time on a small project, though the AI suggestions needed some cleanup before they felt usable. Nice that expert review is built right in.