Case Study Migrating Magento2 to OdooA wholesale company having offices in Sydney, Melbourne,...

Question

Case Study Migrating Magento2 to OdooA wholesale company having offices in Sydney, Melbourne, Brisbane, Adelaide and Perth decided to use Odoo ERP for their various departments and operations such as inventory, sales, marketing, warehouse management, and IT etc. Previously, the company was using various custom-built smaller systems, or different software systems or lacy software systems. Cuently, their product inventory is maintained in Magento2. Transfeing all data from Magento2 to Odoo is a challenge! However, the chief information technology officer came across a magneto-connector application for the Odoo ERP http:odoo-magento-connector.com/index.html . He believes, that this connector application could be a potential solution. The IT department further investigation reveals that there could be possible problems such database fields or keys issue, data types mismatch, relationships between tables etc. The Magentoerpconnector features and technical points are listed at the following link https:apps.odoo.com/apps/modules/8.0/magentoerpconnectand its functions after installation are listed in the following linkhttp:odoo-magento-connector.com/guides/installation_guide.html#after-the-installation The chief information technology office has given you task to prepare a plan for the migration and prepare a quality assurance and testing plan. [Refer to assignment documents to create quality plan, test cases etc for this case study.]      Test Case Template                                         XXXXXXXXXXVersion 1.0        Company Logo Test Case TemplateRough Draft (Version 1.0)      Prepared by:                                          XXXXXXXXXXDate:     Revision History    Date    Issue    Description    Autho                                                                                                                                Date:_______________________________Tested by:      ______________________System:______________________________Environment:      ___________________Objective: ____________________________Test ID _____________ Req ID   ______Function: _____________________________Screen:    _________________________Version:______________________________Test Type:      ______________________                                                  (Unit, Integ., System, Accept.)Condition to Test:  __________________________________________________________________________  __________________________________________________________________________  __________________________________________________________________________  __________________________________________________________________________Data/Steps to Perform:  __________________________________________________________________________  __________________________________________________________________________  __________________________________________________________________________  __________________________________________________________________________Expected Results:  __________________________________________________________________________  __________________________________________________________________________  __________________________________________________________________________Actual Results: Passed  h Failed  h  __________________________________________________________________________  __________________________________________________________________________  __________________________________________________________________________  __________________________________________________________________________Page 3 of 36/29/2018

Neha · Accepted Answer

Test Case Template
	                                                        Version 1.0
	
	

 Test Case Template
Rough Draft (Version 1.0)
      Prepared by: 
                                                            Date:
     Revision History
	Date
	Issue
	Description
	Author
	
	
	
	
	
	
	
	
	
	
	
	
	
	
	
	
	
	
	
	
	
	
	
	
	
	
	
	
	
	
	
	
Test Plan:
The scope of this test plan is to test the system after migration to the Odoo with the Magento. It will help company to manage the ERP system more efficiently. I have included the unit testing, integration testing, performance testing and system testing. 
	Test No
	Item to test
	Test Description
	Date
	T01
	Security
	To test the security of system and data
	01-06-2020
	T02
	Reporting
	To test for the reports generated by system
	03-06-2020
	T03
	Admin Panel
	To check for the admin panel
	04-06-2020
	T04
	Importing data
	To import the data into the system
	06-06-2020
	T05
	Configurable screens
	The configuration of each screen
	09-06-2020
	T06
	Historic Results
	To test for the past data
	10-06-2020
	T07
	BackUp
	To check for the backup of data
	15-06-2020
	T08
	Usability
	To test the usability of system
	17-06-2020
	T09
	Payment
	To test for the payment methods
	20-06-2020
Date:
_________02-06-2020___________
Tested by:      ______________________
System:
_________Migrating to Odoo______
Environment:      __Odoo__________
Objective: ______To test the security_________
Test ID ____T01_______ Req ID   __01__
Function: ____Data encryption_______________
Screen:    ___Data Storage___________
Version:
_______1.0_____________________
Test Type:      __Unit Testing___________
                                              
    (Unit, Integ., System, Accept.)
Condition to Test:
  The testing is performed to check for the security of data which is stored in the data center. Data Analyst or security officer must implement some extra security measures. Only authorized users are allowed access the system. Antivirus and data encryption algorithms will be used. 
Data/Steps to Perform:
The data must be saved in an encrypted format. The firewalls will be installed, antivirus will be used and encryption process will be implemented. The encryption can be implemented using the encryption algorithm. 
Expected Results:
  The data will be stored in encrypted and secured format. 
Actual Results: Passed  h Failed  h
  Passed
Date:
_________02-06-2020___________
Tested by:      ______________________
System:
_________Migrating to Odoo______
Environment:      __Odoo__________
Objective: ______Reporting _____________
Test ID ____T02_______ Req ID   __02__
Function: ____Reporting / Printouts_________
Screen:    ___Report generation_______
Version:
_______2.0_____________________
Test Type:  __Unit Testing /functionality testing__
                                              
    (Unit, Integ., System, Accept.)
Condition to Test:
All the reports should be allowed to take the printout. The developer, project manager and database analyst and the user can check for the reports whether they can be printed or not.

Case Study Migrating Magento2 to Odoo A wholesale company having offices in Sydney, Melbourne, Brisbane, Adelaide and Perth decided to use Odoo ERP for their various departments and operations such as...

Solution

Answer To This Question Is Available To Download

Related Questions & Answers

Submit New Assignment