Pages
OpenERP / Odoo Testing Strategies
Hey guys , let's understand how to test an Odoo Application Manually
- Flow of testing that what field will be required necessary here or not
- Domain strategy that wheather a one field should be tested by perticular level of domains or not
- Dependent field valudations means if 2 fields are dependent or may be one change event effects another field then wheather they are working properly or not
- By overviewing lines fields checking that wheather they are perfectly matching with forms/wizards or not
- When checking workflow & the older version is available then check that wheather it is running perfectly or not
- Checking that wheather required fields are taken perfectly or not
- Specialise in invoice flow that whather they are running perfectly or not
- When onchange is made on another field then try to analyse that wheather that is perfect or not
- In reports , try to check that wheather they are printed prfectly as per the requirement or not
- When talking about user rights then try to check that if priviliged menu is visible to a user or not
- In workflow , wheather different kinds of buttons are seen to a priviliged user or not
- Specialise in a payroll , it means in general scenario they are affected with ( Loans , Expenses , Allowences ) So if u r definding them then u have to take it in mind that payroll salary computation will get affected with that
- When checking new version with older version , try to follow the security rules of older version , a security.csv file is attached with every module so try to observe user rights , they are defined by their objects
- Specially problem will arise in from date & to date field in every module , this is a common mistake made by developers
- Taking a negative age is a common mistake made by developers so first of all check it
- Sometimes some dependency relationships are quite often in nature means unless when u left it blank then it will not allowed u to fill dependent field that causes an integrity error , so at that time developers have to put an appropriate error message that can be easily understood by even a non technical user
- In allowences , when u have specially defined it in a configuration menu then get check that by not giving it means by default they are taking which values in a field
for ex . in
configuration u have taken mobile allowence as 200 Euro for a group A
so when definding group A it should be taken 200 Euro
- Try to avoid commence sense things but also talk once to developer , come on there will not a robot on a pc
- Some times some views are not perfect but it will not be considered in a developer's mistake , it can be a framework mistake
- When working with user rights , try to understand verification & authorization of each user perfectly & flow according to that user
- Take a real time example of a perticular situation that u r handling then try to test with that logic & circumstances
- When checking with user roles specially check more information ( notebook tag in form view ) , ( approved by , published by , modified by ) fields
- When testing in different types of frameworks , first of all u have to consider a structure & limitations of that framework
Subscribe to:
Explore Videos
No comments:
Post a Comment