AutomationNG vs. BugTracker.net

AutomationNG is best suited for people with no programming language at all. It is easy to write tests and execute. Cross browser testing feature is the best part of this app. Cross browser testing can be tricky in other tools, but this app handles it very graciously. However, the tests are executed slowly compared to other tools like selenium but that requires programming knowledge

Incentivized

See above. Recommended questions: What type of feedback or tracking will we be doing? Will this need to be client-facing? How will we track content edits? How many users will be assigned to issues in a given project?

Incentivized

• Doesnt require any programming knowledge
• Test cases are written in simple English-like
• Cross browser testing is supported and is easy to perform
• Integration with Jira
• Takes significantly less time to write test scripts

Incentivized

• Ability to split our multiple projects and assign a user base.
• Ability to set permissions based on user base/ roles.
• Customization of fields on a project level.

Incentivized

• UI is pretty outdated and needs major revamp
• Test results UI can be improved
• Speed of automation can be improved

Incentivized

• User interface for client-facing feedback
• Content and design updates tracking

Incentivized

I would plan on renewing and staying with BugTracker.net simply because it is a no nonsense easy to use tool. Once you get it set up and understand the small nuances with this custom piece of software, it really is a great tool to help your organization get started with Defect Management and BugTracking without having to drop several thousands of dollars on tools that are more fluff than function.

Incentivized

I didn't choose the product or evaluate other options, but I've been satisified with it except for tracking content changes.

Incentivized

• Easy to write the test cases hence saves lot of time.
• Helps us to manage the tests and identify bugs quite early
• Cross browser testing is a major feature

Incentivized

• Decreased turn around time for defect fixes.
• Smoother builder deploys
• Clearer communication from QA to Dev Team

Incentivized