Testing NEOSYS: Difference between revisions
From NEOSYS Technical Support Wiki
Jump to navigationJump to search
m (Arya moved page Lightning Test on NEOSYS to Testing NEOSYS: The page not only talks about Lightning Test, but Testing in general) |
No edit summary |
||
Line 1: | Line 1: | ||
=== Testing | === General Instructions for Testing NEOSYS === | ||
Everytime | #Everytime a new version of NEOSYS is released, it must be tested thoroughly for all its features to ensure NEOSYS credibility to clients. | ||
#Tests for each module must be carried out by logging in as different users as some issues do not show up when logged in as NEOSYS user. | |||
#Testing must be done primarily on the 2nd line when there are multiple rows because many errors do not show in the first line and only show in the subsequent lines. | |||
===Lightning Test=== | |||
===== | Lightning Test is a quick test of NEOSYS where all essential features mostly used by clients must be tested. | ||
'''Lightning Test for all the modules in NEOSYS should not take more than 2 hours. All the tests listed below with an asterisk are mandatory and the rest can be skipped in a Lightning Test.''' | |||
=== List of Tasks to be tested for each module === | |||
===== Media ===== | |||
{| style="width: 60%; height: 100px; text-align: left ; margin: 1em 1em auto;" border="1" | {| style="width: 60%; height: 100px; text-align: left ; margin: 1em 1em auto;" border="1" | ||
Line 54: | Line 60: | ||
===== | ===== Finance ===== | ||
{| style="width: 60%; height: 100px; text-align: left ; margin: 1em 1em auto;" border="1" | {| style="width: 60%; height: 100px; text-align: left ; margin: 1em 1em auto;" border="1" | ||
Line 88: | Line 94: | ||
|} | |} | ||
===== | ===== Jobs ===== | ||
{| style="width: 60%; height: 100px; text-align: left ; margin: 1em 1em auto;" border="1" | {| style="width: 60%; height: 100px; text-align: left ; margin: 1em 1em auto;" border="1" | ||
Line 135: | Line 141: | ||
===== | ===== Timesheets ===== | ||
{| style="width: 60%; height: 100px; text-align: left ; margin: 1em 1em auto;" border="1" | {| style="width: 60%; height: 100px; text-align: left ; margin: 1em 1em auto;" border="1" | ||
Line 164: | Line 170: | ||
===== | ===== Support menu and Help menu ===== | ||
{| style="width: 60%; height: 100px; text-align: left ; margin: 1em 1em auto;" border="1" | {| style="width: 60%; height: 100px; text-align: left ; margin: 1em 1em auto;" border="1" |
Revision as of 11:43, 4 May 2015
General Instructions for Testing NEOSYS
- Everytime a new version of NEOSYS is released, it must be tested thoroughly for all its features to ensure NEOSYS credibility to clients.
- Tests for each module must be carried out by logging in as different users as some issues do not show up when logged in as NEOSYS user.
- Testing must be done primarily on the 2nd line when there are multiple rows because many errors do not show in the first line and only show in the subsequent lines.
Lightning Test
Lightning Test is a quick test of NEOSYS where all essential features mostly used by clients must be tested.
Lightning Test for all the modules in NEOSYS should not take more than 2 hours. All the tests listed below with an asterisk are mandatory and the rest can be skipped in a Lightning Test.
List of Tasks to be tested for each module
Media
List of Tasks | |
---|---|
* | Create a new plan |
* | Check Plan Look up |
* | Create a plan by copying from a plan/schedule |
* | Take a plan printout, make use of filters on the screen |
* | Create a new schedule |
Check Schedule Look up | |
* | Create a schedule by copying from plan/schedule |
* | Use shortcut keys like tab/f9/f7 etc while creating the schedule |
* | Add vehicles with notes/Rate cards |
* | Enter discount and fee for the vehicles |
* | Check if discount and fee gets reflected in the cost and bill |
Create free ads | |
Check if free ads reflect in the reports | |
* | Book ads |
* | Certify ads |
* | Invoice ads |
* | Generate media diary |
Generate progress summary | |
* | Do cancellations |
* | Generate credit notes |
Finance
List of Tasks | |
---|---|
* | Create a new batches (INV/PUR/PAY/PUR) in Journal entry page |
Check the Journal Setup page | |
* | Check Voucher file/deallocation |
Generate the List of Vouchers | |
* | Generate a Ledger print |
* | Check the Statement of Accounts |
* | Check the Chart of Accounts file |
* | Generate Trial Balances |
* | Generate Financial Statements |
* | Check the Currency & Exchange Rate file |
* | Edit the Company file |
* | Check if discount and fee gets reflected in the cost and bill |
* | Test three basic styles of journals e.g "SIDE BY SIDE" format for Sales invoices, "MAIN ACCOUNT IN THE HEADING" format for Bank Payments, "VERTICAL" format for General journals(JOU). |
Jobs
List of Tasks | |
---|---|
* | Create new Job |
* | Check Job Look up |
* | Copy a job |
* | Enter all details |
* | Look up for Job Types |
Use shortcut keys tab/f9/f7 | |
* | Create Estimate |
* | Create Purchase Order |
* | Generate invoice in Estimates |
* | Check invoice gets reflected correctly in Purchase order |
* | Enter supplier invoice for Purchase orders |
* | Check whether all above changes get reflected in the Job file |
Create Credit Notes | |
* | Job printout |
* | Purchase Order printout |
* | Estimate printout |
* | Minutely verify reports to check data consistency |
Generate "List of Jobs pending estimates" | |
Generate "List of Jobs with WIP/Accrued Cost" |
Timesheets
List of Tasks | |
---|---|
* | Edit the Timesheet configure Configuration file |
* | Edit existing activities in Activity file |
* | Create new activities in the Activity file |
* | Create a new Timesheet for a user, test each and every field |
Take Timesheet printouts, test all the options available | |
Test Approval emails according to the users in the Configuration file. | |
* | Test Reminder emails |
Generate Timesheet Analysis report using various filters. | |
* | Generate invoice in Estimates |
Save the report in Excel and verify the records present. |
List of Tasks | |
---|---|
* | Create a new user in the Authorization File and save it |
* | Edit and save the System Configuration File |
* | Edit and save the User Details page |
* | Login as a User group to check all locks/keys are working properly |