...
- 1 I am a tester, how do I go about testing KC? ( edit)
- 2 What is Jira? ( edit)
- 3 Where should I go to test Kuali Coeus? ( edit)
- 4 How and where do I record any bugs that I find? ( edit)
- 5 A bug stopped me from testing, should I set it to Blocker priority? ( edit)
- 6 What is the backdoor login and when should I use it? ( edit)
- 7 I got an exception error, can I just insert a screenshot of an exception error in my bug report? ( edit)
- 8 What's the quickest way to enter a new bug? ( edit)
- 9 Why did I not get an email when I submitted my proposal to Grants.gov? ( edit)
- 10 What should I do with all of the jira@kuali.org email messages I receive? ( edit)
- 11 How do I use Contour to do my testing? ( edit)
- 12 How do I use Filters in Contour to find My Testing Assignments? ( edit)
- 13 I'm a QA Lead, how do I review new issues? ( edit)
1.
I am a tester, how do I go about testing KC? (edit)
These are the main things you need to know to test (well, almost!). Your Testing Coordintor Coordinator or QA Lead may have additional instructions for you and as things change during QA. You may also see instructions that modify or change what is state here on our email list service. (For additional information on the Roles and Responsibilities of our QA Team members please see: KC QA Team Roles and Responsibilities).
1. Test Kuali CoeusFinancial System (KFS)
- Run your tests on the environment specified for the release you are testing.
- Please review the "Test Environments" heading on the QA home page for up to date information on the use of all environments.
- You will find your test script assignments listed in Contour Jira.
2. Recreate the Bug
- Using the steps that created the bug, make sure you can reproduce it one more time. It is important you are confident that the bug is reproducible. This will take more time, but we would prefer to empahsize the quality of the bugs rather than the quantity.
- It is a good idea to write down each step you take as you work. Otherwise you may find it difficult to recreate what you did to cause the bug. If you are following the steps in a test script exactly, it is written down for you so you can just copy it from the test script.
...
- Perform a quick check to make sure the bug you are seeing has not already been reported on your team page.
4. Create a bug reportAdd Comments to the Jira issue
- You can use the following link to quickly create a bug issue: Create a bug report (Be sure to log into Jira.)
- Here are step-by-step instructions for creating the bug: How to Enter A bug in Jira.
- Be sure to include the exact steps to recreate the bug.
- If you use the previous link, it will automatically set the issue type to be a "Bug."
- If you want it to be some other issue type, such as an "Improvement," you can re-edit the issue type after you have saved it.
- Note on Exception/Stack Trace Errors: If the application produced an exception error, there will be a big chunk of error text on your screen. Here is a sample of what they look like: KC Exception Error Sample. Please cut and paste the entire error into the bottom of the Description field after your step-by-step instructions for creating the bug. Do not rely on the screen shot to document this error.
...