Difference between revisions of "SMT483G2: Cerebro User Testing"

From SMT Project Experience
Jump to navigation Jump to search
 
(2 intermediate revisions by the same user not shown)
Line 47: Line 47:
 
<!--Sub Header End-->
 
<!--Sub Header End-->
  
<br>
+
{| style="background-color:white; text-transform: uppercase; font-size:14px; font-weight: bold; text-align:center; padding: 5px 0 0 0;" width="100%" height=50px cellspacing="0" cellpadding="0" valign="top" border="0" |
  
[[File:Testing_pyramid.JPG|700px|center]]
+
| style="vertical-align:top;width:25%;" | <div style="padding: 3px;line-height: wrap_content;  border-bottom:5px solid #000000; font-family:helvetica"> [[SMT483G2: Cerebro User Testing| <font color =#272d2d><b>Internal Testing</b></font>]]
==Testing Procedure==
 
<div style="font-family: Garamond; font-size:16px">
 
<p>
 
In general, there are four levels of testing: unit testing, integration testing, system testing, and acceptance testing. The purpose of Levels of testing is to make software testing systematic and easily identify all possible test cases at a particular level.
 
</p>
 
  
'''Testing''':
+
| style="vertical-align:top;width:25%;" | <div style="padding: 3px; line-height: wrap_content; border-bottom:1px dashed #000000; font-family:helvetica"> [[SMT483G2: Cerebro User Testing Stakeholders |<font color =#272d2d><b>User Testing</b></font>]]
  
1. Unit Testing
+
| style="vertical-align:top;width:25%;" | <div style="padding: 3px; line-height: wrap_content; border-bottom:1px dashed #000000; font-family:helvetica"> [[SMT483G2: Cerebro User Testing 2|<font color =#272d2d><b>User Testing 2</b></font>]]
  
A Unit is a smallest testable portion of system or application which can be compiled, liked, loaded, and executed. We use Django to test each module separately.
+
|}
  
:Things to test:
+
<br>
:- CRUD of User Information/ Stored analysis results
 
 
 
 
 
2. Integration Testing
 
 
 
Make sure that integrated system is ready for system testing.
 
 
 
:Things to test:
 
:- JSON analysis results returned correctly on the frontend pages
 
:- User Information E.g. Name, Profile returned correctly on frontend pages
 
 
 
 
 
3. Systems Testing
 
 
 
It involves load, performance, reliability and security testing.
 
 
 
:Things to test:
 
:- Time Performance of each analysis api call
 
:- Load testing of EC2 Instance
 
:- Availability failover test if number of users increase
 
:- Basic Security testing using OWASP ZAP
 
 
 
 
 
4. Acceptance Testng
 
 
 
Acceptance testing is a test conducted to find if the requirements of a specification or contract are met as per its delivery
 
  
:Questions to ask:
+
[[File:Testing.png|1000px|center|testing]]
  
:1. What does this visualization show? On a scale of 1-5, how clear is the visualization.
 
:2. Test frontend screens, e.g. upon login do you see your name?
 
:3. Task based questions. e.g. Login, Get sentiment about a certain keyword
 
 
<!--/Content-->
 
<!--/Content-->

Latest revision as of 18:05, 15 November 2020