0% found this document useful (0 votes)
48 views18 pages

Mp2-Invetory-Fe (Qa)

The summaries are: 1. The application ran smoothly with less errors found in the codebase and browser inspect. A few warnings remained in Vscode. 2. The application again ran smoothly with less errors. A unique key prop error was found in browser inspect. A few warnings remained in Vscode. 3. The application initially had errors but running npm install fixed them. Warnings remained in code and browser inspect found errors. 4. Running npm install allowed the application to run smoothly with some remaining warnings and browser inspect errors found.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
48 views18 pages

Mp2-Invetory-Fe (Qa)

The summaries are: 1. The application ran smoothly with less errors found in the codebase and browser inspect. A few warnings remained in Vscode. 2. The application again ran smoothly with less errors. A unique key prop error was found in browser inspect. A few warnings remained in Vscode. 3. The application initially had errors but running npm install fixed them. Warnings remained in code and browser inspect found errors. 4. Running npm install allowed the application to run smoothly with some remaining warnings and browser inspect errors found.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
You are on page 1/ 18

Project Name: MP2-INVENTORY-FE

MP2 Module Name: Appbar


Release Version: Sprint-1

Pre-condition In order to test the web page, I cloned first the release/sprint-1 repository. Befo
Dependencies: Manually tested, comb through the codes and through the output.

Test Case# Test Title Test Cases

Step 1: Navigate through your Vscode.


Step 2: Click on
Checking of the the src folder Step 3: Click on
TC-MP2-001 Release/Sprint-1 views folder and you will find the first warning.
(Day 1) Step 4:
Navigate through it again and and go to router,
and there is the second warning.

Step 1: Navigate through your Vscode.


Step 2: Click on the
Checking of the src folder Step 3: Click on views
TC-MP2-002 Release/Sprint-1 folder and you will find the first warning.
(Day 2) Step 4: Navigate
through it again and and go to router, and there
is the second warning.
Step 1: Navigate through your Vscode.
Step 2: Click
on the src folder, since most problems are found
in this specific folder.
Step 3: Click on the components folder, find
the Toast folder and click the Toast.js and you
will find the errors exactly at [ln 4, col 48] and [ln
5, col 37]
Step 4: Next, still in the src folder,
Checking of the
navigate through the core folder. As you clicked
TC-MP2-003 Release/Sprint-1
you will be face with the context folder that
(Day 3)
consists of the javascript fille with an error. In
this file the error is exactly found at [ln 6, col 39]

Step 5: The warnings on the other hand is


found the src/view/Home/Home.js at exactly [ln
1, col 8] and src/router/index.js at exactly [ln 8,
col 1]
Step 1: Navigate through your Vscode.
Step 2: Then
access your application by inputting npm start in
your vscode terminal. To do that, kindly call
upon your folder that consists of your react
application. (Open VScode > Terminal > cd
[folder name] > npm start)
Step 3: If the application is not
running, try running npm install in your VScode
terminal and kindly refresh.
Step 4: After the
application is ran, there will be no error other
Checking of the
than the browser inspect one.
Release/Sprint-1
Step 5: The
(Day 4)
warnings on the other hand is found in the:
-
src/router/index.js "Assign arrow function to a
variable before exporting as module default" [Ln
14, Col 1].
- src/views/Blocks/HomeBlocks.js "React Hook
useEffect has a missing dependency:
'handleToastify'. Either include it or remove the
dependency array." [Ln 20, Col 6]
-
src/views/Home/Home.js "'React' is defined but
never used." [Ln 1, Col 8]
TC-MP2-004
Test Designed by: Hammillan Manlanot
Test Designed date: 4/5/2023
Test Executed by: Hammillan Manlanot
Test Execution date: 5-Apr-23

nt-1 repository. Before running the application it was necessary to install npm first for it to start the developm
output.

Test Summary Test Steps

The application run smoothly with less to none


1. Run application in Vscode.
possible errors. As checked in the inspect
2. Application was ran
section of the browser the only error was "each
with the output.
child in a list should have a unique "key" prop."
3. Checked on
Other than a few more warnings in vscode, no
inspect for other errors.
more errors were found.

The application run smoothly with less to none


1. Run application in Vscode.
possible errors. As checked in the inspect
2. Application was ran
section of the browser the only error was "each
with the output.
child in a list should have a unique "key" prop."
3. Checked on
Other than a few more warnings in vscode, no
inspect for other errors.
more errors were found.
The application didn't ran smoothly due to errors 1. Run application in Vscode.
that where found inside the codebase. As
checked in the inspect section of the browser 2. Application ran in the
there was also an error related to what is found browser 3.
when running the application. Other than a few Checked on inspect for other
more warnings in vscode, no more errors were errors and checked in vscode for
found. warnings.
1. Run application in Vscode.
The application finally ran smoothly, the errors
were fixed by typing npm install in the vscode
2. Application ran in the
terminal. However, there is still warnings inside
browser 3.
of the code and a few errors in the browser
Checked on inspect for other
inspect section. In conclusion errors were found
errors and checked in vscode for
but the application still ran smooth and visible.
warnings.
it to start the development server.

Test Data Expected Result

* The code is clean and working


1. Codes pulled from
properly
release/sprint-1 into Vscode.
* Code has less to none
2.
errors * The
Output of the Application
output is visible

* New pull requests


* The code
1. Codes pulled from
is clean and working properly
release/sprint-1 into Vscode.
* Code
2. Output
has less to none errors
of the Application
* The output is
visible
* New pull requests
* The
1. Codes pulled from
code is working properly
release/sprint-1 into Vscode.
* Code have less to none errors
2.
* The
Output of the Application
output is visible
* New pull requests
* The
1. Codes pulled from
code is working properly
release/sprint-1 into Vscode.
* Code have less to none errors
2.
* The
Output of the Application
output is visible
Post-condition

The application was ran smoothly.

The application was ran smoothly.


The application didn't ran at all. It
has errors in the codes.
The application finally ran
smoothly after npm install was
input.
Actual Result Status

1. The code had warnings. - React in


src/views/Home/Home.js is defined but was never used [ln
1, col 8].
- "Assign arrow function to a variable before exporting
as module default" warning in src/router/index.js [ln 8, col The application is
1]. 2. The output is visible and still under
working fine. 3. The animations like development.
hover on buttons are working properly and is interactive.
4. Browser inspect has an error "each
child in a list should have a unique "key" prop."

1. New pull request where found


2. The code had warnings.
- React in
src/views/Home/Home.js is defined but was never used [ln
1, col 8].
- "Assign arrow function to a variable before exporting
The application is
as module default" warning in src/router/index.js [ln 8, col
still under
1]. 3. The output is visible and
development.
working fine. 4. The animations like
hover on buttons are working properly and is interactive.
5. Browser inspect has an error "each
child in a list should have a unique "key" prop."
* There is new pull request a Card and
Button component
1. New pull requests were found
2. The codes have errors
- Error found in
src/components/Toast/Toast.js [ln 4, col 48]
* Module not found: Error: Can't resolve 'react-toastify'
- Error found in
src/components/Toast/Toast.js [ln 5, col 37]
* Module not found: Error: Can't resolve
'react-toastify/dist/ReactToastify.css'
- Error found in src/core/context/MessageContext.js [ln 6,
The application is
col 39]
still under
* Module not found: Error: Can't resolve 'react-toastify'
development.
- Uncaught error in browser
inspect (Uncaught Error: Cannot find module 'react-
toastify') 3. The output isn't available
due to the errors. 4. Warnings are still
visible -
React in src/views/Home/Home.js is defined but was
never used [ln 1, col 8].
- "Assign arrow function to a variable
before exporting as module default" warning in
src/router/index.js [ln 8, col 1].
1. New pull requests were found
2. The application output is
visible 3. There was
still an inspect error in the browser. Stating "Warning:
Each child in a list should have a unique "key" prop."
The application is
4. Warnings are still visible
still under
- React in
development.
src/views/Home/Home.js is defined but was never used [ln
1, col 8].
- "Assign arrow function to a variable before exporting
as module default" warning in src/router/index.js [ln 8, col
1].
Notes

You might also like