Atlassian Interview Question
Test Automation Goal: To demonstrate your ability to design and implement valuable automated tests. Task Write two automated browser-based tests for Confluence Cloud, our hosted wiki product: • One that tests that a user can create a new page. • One that tests that a user can set restrictions on an existing page. Details • Sign up for a free trial of Confluence Cloud at https://www.atlassian.com/software/confluence/try/ . This will provide you with 7 days of free access to a hosted Confluence instance. No credit card is needed. • Use Selenium 2.0 (aka WebDriver): http://docs.seleniumhq.org/projects/webdriver/ • Implement the page objects pattern: http://code.google.com/p/selenium/wiki/PageObjects - or tell us why your alternative approach is better. • Write your test in any language WebDriver supports.
Interview Answers
Anonymous
Exploratory Testing Goal: To demonstrate your approach to manually testing a feature without using specifications or scripted test cases. Task: Perform 30 minutes of exploratory testing of the Confluence Page Tree feature to investigate if this feature is of high quality. Decide what further testing of the feature would need to be performed before you would ship it to production. Details • Use the same Confluence instance that you created for the previous exercise. • You will be testing the Page Tree. This feature displays all the pages in a space in an expandable and collapsible tree. It allows the user to rearrange these pages by drag-dropping. • This feature can be accessed by clicking “View in Hierarchy” from the “...” menu in the top-right corner on any page in a space. • The scope of this exercise is limited to the tree view feature only, under the “Reorder Pages” tab. You should not test the other tabs (Orphaned Pages, Undefined Pages, etc) or other Confluence features, unless they will help you to assess the quality of this feature. • You should explore to discover other functionality offered by this feature. • As this exercise is aimed at assessing your exploratory testing approach and not the total number of bugs found, there is little value in continuing beyond the allocated 30 minutes.