Workday Data Toolkit Bug Hunt

Appirio's Workday Practice would like to develop a Data Management application for assistance in Workday implementation projects.  There is a set of data-related tasks that the practice is hoping to automate:

1. Producing a data dictionary for a project
2. Producing data gathering workbooks for a project
3. Validating data from data gathering workbooks.
4. Mapping data from data gathering workbooks to ILoad sheets
5. Transforming data gathering workbooks to ILoad sheets.

This initial phase will focus on the first three high level requirements.

 

You will be testing the web application for both Admin and Project User.

In the forums we will provide the web application. Use "/docs/Workday Data Toolkit Schema and Workbook Frontend Phase 2 Part 1 Assembly Deploy Guide" as the deployment guide, as it is the latest one.

Here are a few deployment steps for a quick introduction:

1. You need to have PostgreSQL installed, with an empty "WDT" database created.
2. You need to set the PostgreSQL user/password in "/wdt/pom.xml" and "/wdt/src/main/resources/META-INF/persistence.xml". Also check if you need to replace the URL for PostgreSQL (change the IP to localhost, or your own IP)
3. You need to have Maven installed.
4. From console, execute inside the "/wdt" folder this command "mvn package -DskipTests".
5. Then, deploy the "/wdt/target/wdt.war" file inside Tomcat (copy it in the "/webapps" folder of Tomcat).
6. Access https://localhost:8443/wdt and start checking the application.
7. Use Admin user: name="admin", password="admin".
8. Use Project User: name="user1", ..., "user10", password="test".
9. Unit Test issues are also accepted, so you may check them also. Other issues found directly in code are also accepted.

We have Wireframes and a Storyboard Design, but they are kind of out of date. In order to avoid confusion we will not provide them in the forums.

We will provide only the initial application requirements and the Architecture documents. Some things have changed since they were produced, so you may need to ask in the forums if you have doubts.

The application will be deployed only on the local system, not in Heroku or Amazon EC2, so you should ignore the references to them.

The guidelines for this contest are given below:

• As issues are identified they need to be logged in JIRA.
• Issues must include clear descriptions, test cases and steps to reproduce and expected vs. actual results in order to be counted.
• First competitor to find an issue gets credit, duplicates will not be counted.
• Reviewers will accept, reject or mark the issues as duplicate.
• Please DO take a look at the reported bugs, duplicated bugs cost your work time and the reviewer's time.
• Please focus on functional testing of the web application. We don't need bug reports on typos, spelling errors and any trivial issues like this, so all such issues will be rejected and will not count

 

Final Submission Guidelines

Bug Report Format

For each report of a limitation or bug, we need the following information:

• Steps to reproduce, including any needed information
• Screen shots (if applicable)
• Expected results after the bug is fixed
• Current results, before the bug is fixed

You will log your tickets here: https://apps.topcoder.com/bugs/browse/WORKDAYBUGHUNT.

Scoring

Some of the tips helpful for the contest are:

• Submitting what is obviously the same issue multiple times with small variations will only annoy the reviewer that has to sort through all the issues and will only count as one issue anyway. If it's less obvious if it is the same issue or not, use your best judgment and the reviewers will do the same.
• Put an eye on the issues being submitted by other members to minimize the time you may be spending on duplicate efforts. Knowing what has already been reported will allow you to better focus your time on finding yet undiscovered issues.
• Double check your steps to reproduce and test cases to make sure they are clear. Make sure your steps include creation of any necessary data.