...
updated: KHensley, 2010-03-05 Fri 3.
Where should I go to test
...
KFS?
...
Each release has has its own server with a copy of the application. Please check with your Testing Coordinator or one of the QA Leads to make sure you are using the correct environment for your release. Occasionally during a project, the environment we are using to test may change. We will let you know via email and in the News and Announcements section of your release page.
...
How to Login? Unless otherwise instructed by your QA Lead or the test script your are using, login as quickstart (there is no password) updated: S. Heise: Friday, July 9, 2010 4.
How and where do I record any bugs that I find?
...
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 Feedback Feedback" project (note the project still uses acronym of KC's old name: "KRA" for "Kuali Research Administration"). updated: S. Heise, 2010-07-09 Fri
5.
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 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.
...
- An important module, Proposal or Budget say, in the application is rendered unusable or unavailable. For instance, you cannot search for or open existing Proposals or you cannot create new ones.
- There are seriously lost or corrupted data, such as situations where you cannot save a proposal or budget or data is transmitted to a grants.gov form that would have serious consequences or prevents submission.
- The issue is affecting all users and not just a single or small group of users.
- The application as whole is completely down and is preventing anything from being tested. 6.
What is the backdoor login and when should I use it? (edit)
- The back door login is a feature that allows you to login as a new person without first logging out
- Testing while logged in using the backdoor feature is definitely not recommended - especially for permissions. Testing this way cannot be considered conclusive and bugs will be sent back to you for retesting
- Please open a new instance of your browser and login with the user that has the permissions you are trying to test.
7.
I got an exception error/stack trace, can I just insert a screenshot of an exception error in my bug report? (edit) - 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 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 QA Reporting Issues in JIRA - KRAFDBCK
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 KC?
updated: S. Heise, 2010-07-09 Fri
9.
Why did I not get an email when I submitted my proposal to Grants.gov? (edit)
- All emails from proposals submitted by the KC test system are sent to the email address KC.Grants.gov@kuali.org. This is a Sakai site (a tool we use for managing group emails, among other things and you need to be added to the group membership on Sakai.
- Since all the emails from submitted proposals are sent to one list, you will have to sort through the emails to find those for your specific proposal so will need to remember you Grants.gov submission ID.
- Sakai creates an email archive which you can access here: Grants.gov Email Archive
- Administrators:
o Tyler Wilson (Tyler.Wilson@Research.ColoState.edu) is the keeper of the list.
o Kenton Hensley (kh394@cornell.edu) can also help out if Tyler is not around.
in Jira: Create Bug Report
Fill in all the fields according to these instructions: KC QA Reporting Issues in JIRA - KRAFDBCK
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 KC? updated: KHensley, 2009-01-28 Wed
10.
What should I do with all of the jira@kuali.org email messages I receive? (edit)
The JIRA bug tracking system will send automatic email messages to the Reporters and Assignees of any JIRA issues, so when you create a new issue you will receive email updates any time that JIRA is modified. The QA process itself updates the status of a JIRA several times as the issue moves through the system, so you can expect to receive several email messages from jira@kuali.org for that issue alone. You might create a rule to filter and move these messages to a different folder so your Inbox doesn't get cluttered. It's important to at least read the most recent email message received for each JIRA, as it will often have comments or questions from the QA team or Developers for the Reporters (testers). 11.
How do I use
...
Jira to do my testing?
...
Contour is the tool used by QA which contains all of the test scripts. There is a report which shows which testers are assigned to which test scripts. Contour is also the location where pass/fail is recorded for each test 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 KC?
12.
How do I user filters to find My Testing Assignments? (edit)
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 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.
...