...
These are the main things you need to know to test (well, almost!). Your Testing 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 Financial System (KFS)
...
- 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 emphasize 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.
...
- 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 KFS 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.
...
- When your issue has been fixed, you need to confirm that it really was fixed to as you expected it. This means you need to retest KC KFS for the issue.
- Retest for the bug as soon as possible after you learn of the fix. As a team managing issues and work gets difficult and inefficient if the bugs are not addressed quickly - thank you for helping with this!
- What to do when the bug is fixed or if it is not:
1. If fixed - close the bug and comment that you retested and found it fixed. In the comment, indicate how you tested if you did not use the exact same steps or data as you outlined in the original bug description.
2. If bug is not fixed - reopen the bug with a comment saying why you are reopening it. - Please note: If you found an unrelated bug, create a new bug report - don't use the existing bug report for anything new. Continue to monitor for complete fix. - Remember Testers! You are not done with a bug until you have confirmed it is fixed and you have closed it. Please!
...
The Kuali projects use an issue tracking tool called Jira. People working on the project will also refer refer to these issues as "Jiras." If someone says to you, "Could you please create a Jira for that?" they mean please record the issue using, our web-based, issue tracking software of the same name. Each of the Kuali software projects has serveral Jira projects to keep the bugs and issues organized. The one where we enter bugs for Kuali Coeus is known as the QA Feedback project. It's shorthand name is KRAFDBCK. Each issue in a Jira project is given a unique ID which consists of the short name and a number as in KRAFDBCK-199. If you have that number you can always find your bugs by entering them in the Jira search box at the top right of the screen. Here is s a link to the Jira, "KRA QA KFS Feedback Feedback" project (note the project still uses acronym of KC's old name: "KRA" for "Kuali Research Administration").
A bug stopped me from testing, should I set it to Blocker priority?
- Well of course, it all depends. It is natural to think that if you cannot proceed with testing that you are "blocked" and that this means the priority is Blocker. However, what is a priority in one context is not in another. In the case of "Blocker" we think big - in terms of the application or an entire Module as a whole.
- In KC KFS we we use Blockers for really serious issues with a big impact to testing or the application. If you are asked to test the Sponsor Lookup and you click on the icon and nothing happens, you may well consider yourself blocked. But in terms of the Application and Module, it turns out it is not so severe because you find you can enter the sponsor if you know the ID and you can find the ID in the maintenance document. It maybe critical, but certainly not a blocker.
- Also, please note that setting Blocker priority sends emails to the DMs, QA Manager and QA Leads and everyone "hops to it" with the old Adrenaline rush.
...
- Please include both the text as well as a screenshot of the entire screen (press Alt-PrtScn).
- The disadvantage of screenshots is that they are not searchable and this makes it hard to find them. Screenshots, on the other hand, may convey some information to the developer that the exception will not.
- To include the text, copy the big chunk of error text on your screen and paste it at the end of the step-by-step instructions you provided for creating the bug.
- Here is a sample of what exception errors look like: KC KFS Exception Error Sample.
What's the quickest way to enter a new bug?
The following link will save you some clicks two and directly open a blank bug report screen for the QA Feedback project in Jira: Create Bug Report
Fill in all the fields according to these instructions: KC KFS QA Reporting Issues in JIRA - KRAFDBCKKFSFB
Please remember, that other than this, there are no shortcuts to entering a quality bug report! Please see I am a tester, what do I need to do to test KCKFS?
What should I do with all of the jira@kuali.org email messages I receive?
...
- Sign into Contour https://contour.kuali.org/
- Click on "Reports" button in upper right
- Under the Global Reports tab, click on "!KC KFS - Testing Assignments & Status (by Team and Tester)"
- Choose your output, HTML or PDF
- Click "Run Report" button at the bottom
- This list is sorted by team, so scroll down to your team to see your list of scripts to test.
- Click on the blue ID link to pull up the script.
...
- On the QA Home page, left hand side is the heading Testing Team Pages, click on our team, "Proposal Workflow and Award Workflow"
- At the bottom of the page is a header, "Proposal Workflow and Award Workflow Issues Requiring Retesting"
- It is your responsibility to retest the script once it appears here.
- Follow the instructions in section(g) of I am a tester, how do I go about testing KCKFS?
How do I user filters to find My Testing Assignments?
You can use the reports or filters in Contour to find your assignments. Most testers find that the filters are easier to use because, unlike the reports, opening a test scripts or test analyis analysis item does not open a new browser session or browser tab (depending on your Browser's settings) each time you click a link. Instead, it opens a new tab in Contour and you can see and work with all your items more easily. The following steps will give you an idea of how to do it. Click the image below for an overview. There is more information in the steps below.
...