VISME TEST PROCESS
VISME TEST PROCESS
a location connected to the internet that maintains one or more pages on the World Wide Web (www)
a procedure intended to establish the quality, performance, or reliability of a software, especially before it is taken into widespread use.
a notable aspect of a device or software application.
the process of testing changes of software to make sure that the previous code still works with the new changes.
testing that your product meets the specifications or requirements you have written.
able to be reproduced, replicated, or copied.
an error, flaw, failure or fault in a computer program or system that causes it to produce an incorrect or unexpected result, or to behave in unintended ways.
changes made to the code to correct an error, flaw, or fault in the software.
basic techniques in finding and logging bugs
Understand the whole application or module by doing in depth testing.
Perform repeated tests with different test environment. In our case, test it in all available supported browser.
Last and the best trick is try very hard to find the bug. Be meticulous in your own way. .;-) As if you are testing to break the application!
When you think that you have completed most of the test conditions and when you think you are tired somewhat then do some monkey or adhoc testing and exploratory testing.
1. Open and Log-in to JIRA
Click the texts above to go to Visme's Page in JIRA.
2. Select Issue Type
this depends on the item you want to log into JIRA. If it is "for Improvement or New Feature", you can choose Story. If it is a bug or flaw of the system, choose Bug.
3. Provide a Short but Catchy Summary
the summary of the bug should contain what you want to convey so the developers or anyone's reading it has already an idea before even reading the description.
4. Set the Priority of the Issue
this depends on the severity or impact of the issue. If it talks about a crash or website cannot be accessed, and is reproducible in any browser, set the priority to "Highest/High". If the issue is occurring in a particular steps or scenario or browser, you can set that to "Medium". If it's for improvement or suggestions, set it to "Low/Lowest". After all, it's a case to case basis.
5. Provide a Detailed Description
in this section, you can write all you have to write about the issue - the steps to reproduce the issue, the browsers/environment in which the issue can be reproduced, the platform used (Windows/MAC/Linux), and more importantly the versions of the browsers used. If you can provide more than that, much better. Attach a video on how you reproduced the issue if possible.
6. Provide Screenshots
aside from log files, screenshots are very useful for the developers or anyone who's viewing the issue. Because sometimes, by just looking at the screenshots, someone will understand what is the issue.
7. Set Label
usually, this is set to "Bug" or "Feature". Bug is selected if the filed item on JIRA is a bug. Feature is selected if the filed item on JIRA is a "for improvement".
Rachel CE | Tester/Technical Support | VISME