Confluence is a collaboration and content sharing platform used primarily by customers who are already using Atlassian's Jira project tracking product. The product appeals particularly to IT users.
$6.40
per month per user
Azure Test Plans
Score 9.1 out of 10
N/A
Azure Test Plans is an exploratory test toolkit available from Microsoft's Azure suite of services. It enables manual testing for users, so that they can plan, execute, and track scripted tests with actionable defects and end-to-end traceability. Assess quality throughout the development lifecycle by testing your desktop or web applications. It is available with Azure DevOps Services.
N/A
Pricing
Atlassian Confluence
Azure Test Plans
Editions & Modules
Free
$0
Free for 10 Users
Standard
$6.40
per month per user
Premium
$12.30
per month per user
Data Center
220,000.00
40,001+ Users - Annually
Enterprise
Contact Sales
No answers on this topic
Offerings
Pricing Offerings
Confluence
Azure Test Plans
Free Trial
Yes
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
Prices shown here reflect prices for deployments with 100 users or less. The prices decrease wien the user base surpasses 100.
—
More Pricing Information
Community Pulse
Atlassian Confluence
Azure Test Plans
Considered Both Products
Confluence
No answer on this topic
Azure Test Plans
Verified User
Engineer
Chose Azure Test Plans
Test rail feels quite dated compared to Azure Test plans and Devops as a whole. Functionality and ease of use is actually night and day.
The ability to create structured test plans with ease that can be traced and attached to Epics and stories with relevant tasks allows the …
I would recommend Atlassian Confluence for companies that want to have internal documentation and minimum governance processes to ensure documentation is useful and doesn't have a lot of duplicated and non-updated content. I wouldn't recommend Atlassian Confluence for companies with a low budget since this product might be a little costly (especially with add-ons).
It works well for express test case implementation with a short duration. You can define the tests for two weeks and run the activities documenting the software errors and fixes to control the effectiveness of DevOps. The graphic reports give the idea of the backlog phases advances and errors detected. It needs improvement if you have a large test project and need to design financial budgets and control over costs of the test plan.
Cross product linking - If you use other Atlassian products then Atlassian Confluence is a no-brainer for your source of documentation, knowledge management etc. You can show previews of the linked asset natively E.g. showing a preview of a JIRA ticket in a Atlassian Confluence page.
Simple editing - Though the features available may not be super complex right now, this does come with the benefit of making it easy to edit and create documents. Some documentation editors can be overwhelming, Atlassian Confluence is simple and intuitive.
Native marketplace - If you want to install add-ons to your Atlassian Confluence space it's really easy. Admins can explore the Atlassian marketplace natively and install them to your instance in a few clicks. You can customise your Atlassian Confluence instance in many different ways using add-ons.
UI Design is very simplistic and basic could make use of more visually interesting colour choices, layout choices, etc.
Under the 'Content' menu, it defaults to having a landing page for all L1 and L2 category pages. Meaning as long as the broader content category has a sub-category, it still creates a separate landing page. In my team's case, this often creates blank pages, as we only fill out the page at the lowest sub-category (L3).
Hyperlinks are traditionally shown as blue, however, this results into very monotonously blue pages in cases where a lot of information is being linked.
I am confident that Atlassian can come with additional and innovative macros and functions to add value to Confluence. In 6 months, Atlassian transformed a good collaborative tools into a more comprehensive system that can help manage projects and processes, as well as "talk" with other Atlassian products like Jira. We are in fact learning more about Jira to evaluate a possible fit to complement our tool box.
Great for organizing knowledge in a hierarchical format. Seamless for engineering and product teams managing software development. Helps in formatting pages effectively, reducing manual work. Tracks changes well and allows for easy rollbacks. Granular controls for who can view/edit pages. Search function is not great which needs improvement. Hire some google engineers
We never worked against the tide while using Confluence. Everything loads considerably fast, even media components like videos (hosted on the platform or embed external videos from Youtube, for example). We are not using heavy media components a lot, but in the rare occasion we happen to use one we have no problems whatsoever.
This rating is specifically for Atlassian's self-help documentation on their website. Often times, it is not robust enough to cover a complex usage of one of their features. Frequently, you can find an answer on the web, but not from Atlassian. Instead, it is usually at a power user group elsewhere on the net.
We chose Atlassian Confluence over SharePoint because it's much more user-friendly and intuitive. Atlassian Confluence makes collaboration and knowledge sharing easier with its simpler interface and better search. While SharePoint can be powerful, it often feels clunky and complex, making it harder for our team to actually use it.
We're doing a full continuous integration (CI), continuous delivery (CD), continuous testing (CT), security, delivery, and monitoring. They have been lately adding features to the services on a regular basis. Every two weeks, they add functionality to Azure DevOps Services to match it with what Azure DevOps Server or on-prem would offer. So, we continue to get more robust functionality. My favorite right now is that they are starting to open up the API availability within Azure DevOps Services.