If you test your app yourself, you can see if something needs to be fixed but you won't get more opinions about your product. I'd recommend to gather beta testers instead (either through a mailing list or through a query on the social media you and your community are using)
@rubenwolff Thanks for the answer.
But how do you test the existing features when you deploy a new version of your app? Let's say your app has 10-15 core features. Do you test them manually every time when you're about to release?
Hi Andras!
We generally list down top 20-30 - key features (depending on the product) and test them manually before every release. When we could afford more resources - we went with automated testing. However, manual testing is still mandatory after every minor/major release.
@nomoreconfig : To check the newly added UI text and design changes. I work for a security product (password manager) and should be double sure always :)
Hi Andras.
A combination of both automated and manual testing would be your best bet. Depending on the language and framework you are using there should be an automated testing library that can help reduce bugs across releases.
Always test new features manually as well, and then throw in a full system test to be sure. A good thing to do is keep a checklist of all the thinks you've tested, then you can run through and retest before each release and make sure you've not forgotten anything.
Replies
#MatchingVoices Podcast - Season 1
#MatchingVoices Podcast - Season 1
#MatchingVoices Podcast - Season 1
ManageEngine
ManageEngine
HackerPulse