TEST: Difference between revisions

From Calidus HUB
VisualWikitext
No edit summary
No edit summary
Line 1: Line 1:
Marshalls MLP PDA Styling changes
<div class="noprint">
{{#vardefine:Client|TEST}}
{{#vardefine:ClientName|Testing Customer}}
{{#vardefine:System|''CALIDUS'' ePOD}}
{{#vardefine:Doc_Title|Test Document}}
{{#vardefine:Version|0.1}}
{{#vardefine:Date|25th January 2019}}
{{#vardefine:Reference|123456 TEST01}}
{{#vardefine:Year|2019}}
{{ #vardefine: Figure | 0 }}{{ #vardefine: Example | 0 }}
<!--
Sample Xref:
{{Xref
|Type=Figure
|Num={{ #vardefineecho: Figure| {{ #expr: {{ #var: Figure}} + 1 }} }}
|Text=Data Upload - Import screen.}}
-->
</div>
{{Doc_TitleNew
|Client={{#var:ClientName}}
|System={{#var:System}}
|Title={{#var:Doc_Title}}
|Reference=FS {{#var:Reference}}
|Version={{#var:Version}}
|Date={{#var:Date}}
|Year={{#var:Year}}
}}


== Requirements ==
<!-- TOC -->
<div class="noprint">
= FUNCTIONAL OVERVIEW  =
== Client Requirement  ==
<!-- Include a statement describing the client’s work request requirement. -->
Statement


Changes are to the MLP device styling only.
== Solution Overview  ==
<!-- Include a summary of the solution explaining how the client’s requirement will be delivered.  This might be as a result of software development or system configuration and implementation. -->
Statement


* No pagination on styling of products list.


* Switch Long Description and Description on products list
== Scope  ==
<!-- This change will be applied to system version (enter the version) on (enter the test database e.g. CONTST) and once approved (enter the production database e.g.: CONPRD).


* Product Quantity entry to split Packs and Loose to separate lines for actual quantity, plus UOM on second line. Planned quantity to remain the same layout.
Describe the scope of work and be clear about what is included and what is excluded. -->
Statement


For example:


    Actual:    CCCCC /
== Impact ==
                UUUUU  UOM
<!-- Identify the potential consequences of the changes described in this Functional Specification.
    Planned:    CCCCC / UUUUU


== Solution Overview ==
Relating to the scope of work, document any identified dependencies necessary to maintain consistency of the solution. Highlight those not addressed within this solution specification.
The product list defaults to 10 items per page. The style for MLP devices ('MAR-LAND') will be modified so that this has no pages.


Include any considered and related opportunities for improvement not addressed within this solution specification. -->
Statement




<!-- NEW PAGE -->
= CONFIGURATION SET-UP  =
== Pre-requisites  ==
<!-- Think about dependent functionality or configuration that is required to support this deliverable and describe here. -->
Statement




== Menu Structure  ==
<!-- Describe how the menu system will change to accommodate this requirement if relevant. -->
Statement




== Functional Description ==
== Data  ==
=== PDA Style ===
<!-- Document any configuration data set up necessary to enable or control the solution e.g. the new report will be added to the standing data to allow it to be selected from the standard reports form. The selection criteria for the report will be (insert selection criteria). -->
The style for MLP devices ('MAR-LAND') will be modified to achieve the changes required.
Statement


Pagination will be removed from the products list.


== Implementation Advice ==
<!-- Include any relevant notes that will help OBSL or Client implementer to successfully enable the solution on delivery. -->
Statement


{{DevNotes|This will be achieved by adding the following to the 'MAR-LAND' PDA Style:
  "ColDel_lvProductList": {
    "intPageSize": 0
  },
}}


<!-- NEW PAGE -->
= FUNCTIONAL DESCRIPTION =
== Heading  ==
=== Sub Heading  ===
<!-- Describe functionally how the solution will satisfy the client requirement. Include statements to define all of the new capabilities or changes to be developed.  Include pictures to illustrate and support design.


Long Description will be used instead of Description on the Products list.  
Note that this section will usually be reviewed and signed off by the client.  Think about the audience and ensure the information documented is easy to read and understand.


Group the functional description into logical areas and use sub-headings where appropriate -->
Statement


{{DevNotes|This will be achieved by changing the 'MAR-LAND' PDA Style for the product list from:
 
  "ProdList_Items": [
<!-- NEW PAGE -->
    "lblProductID",
= TECHNICAL NOTES =
    "lblPackSize",
== Modules Changed ==
    "lblProductUnitType",
<!-- List the modules or objects that will be changed by this development -->
    "lblProductPlannedQty",
{| class="wikitable" border="1" width:"100%"
    "lblProductDesc"
|-bgcolor="#FFFF99"
  ],
! Module Name !! Module Type !! Notes
to this:
|-
  "ProdList_Items": [
| 1 || 2 || 3
    "lblProductID",
|}
    "lblPackSize",
 
    "lblProductUnitType",
 
    "lblProductPlannedQty",
== Table Updates ==
    "lblLongDesc"
<!-- Detail any changes to the data model including additional tables, columns, indexes etc -->
  ],
{| class="wikitable" border="1" width:"100%"
  "ProdList_lblLongDesc": {
|-bgcolor="#FFFF99"
    "width": "98%",
! Name !! Type !! Nullable !! Default !! Storage !! Comments
    "left": "1%",
|-
    "color": "#000000",
| 1 || 2 || 3 || 4 || 5 || 6
    "font": {
|}
      "fontSize": "16 * Ti.App.resMod"
 
    }
 
  }, 
== Developer Notes ==
}}
<!-- Include technical notes and definitions to assist the developer where appropriate -->
 
 
<!-- MEDIA LANDSCAPE YES -->
= TEST PLAN  =
{{TestPlan_Header
|Title={{#var:Doc_Title}}
|Log={{#var:Reference}}
|Description=description of what is to be achieved
|MenuAccess=Where on the menus the item can be found
|Prerequisites=The prerequisites of the test
|Objective=The details of what each group of tests is to achieve
}}
{{ #vardefine: Cycle | 0 }}{{ #vardefine: SubCycle | 0 }}
{{TestPlan_CycleHeader
|Cycle={{ #vardefineecho: Cycle | {{ #expr: {{ #var: Cycle }} + 1 }} }}{{ #vardefine: SubCycle | {{ #var: Cycle }} }}
|Title=Area being tested in this cycle
|Notes=Any notes or prerequisites for the tests following.
}} <!--INSERT TESTS HERE --> {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=The actions to follow
|Result=The expected result
|Remarks=
|PassFail=
}} {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=The actions to follow
|Result=The expected result
|Remarks=
|PassFail=
}} {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=The actions to follow
|Result=The expected result
|Remarks=
|PassFail=
}} {{TestPlan_CycleFooter}}
 
<!-- MEDIA LANDSCAPE NO -->
{{Doc_AppendixNew
|Appendix=A
|Estimate=Y
|Glossary=EPOD
|Ref1=Reference1
|RefV1=0.1
|RefDate1=01/01/2011
|REQ=0
|EST=0
|FS=0
|TS=0
|DEV=0
|ST=0
|IMP=0
|PM=0
|Client={{#var:Client}}
|Year={{#var:Year}}
|FSEST=Y
|Rev1=Rev1
|Rev1Title=OBS Project Manager
|Rev2=Rev2
|Rev2Title=Customer Representative
}}</div>
[[Category:{{#var:Client}} FS]]

Revision as of 17:30, 25 January 2019





Aptean Logo.png







Testing Customer

Test Document

Functional Specification

25th January 2019 - 0.1
Reference: FS 123456 TEST01















FUNCTIONAL OVERVIEW

Client Requirement

Statement

Solution Overview

Statement


Scope

Statement


Impact

Statement


CONFIGURATION SET-UP

Pre-requisites

Statement


Menu Structure

Statement


Data

Statement


Implementation Advice

Statement


FUNCTIONAL DESCRIPTION

Heading

Sub Heading

Statement


TECHNICAL NOTES

Modules Changed

Module Name Module Type Notes
1 2 3


Table Updates

Name Type Nullable Default Storage Comments
1 2 3 4 5 6


Developer Notes

TEST PLAN

Test Script / Scenario ReferenceTest DocumentCall Number(s): 123456 TEST01
Test Script / Scenario Descriptiondescription of what is to be achievedPASS / ISSUES / FAIL
Menu AccessWhere on the menus the item can be found 
Pre-requisitesThe prerequisites of the testTested By:
 
Test ObjectiveThe details of what each group of tests is to achieveDate:
 



Step Action Result Remarks P/F
1 Area being tested in this cycle      
  Any notes or prerequisites for the tests following.      
1.01 The actions to follow The expected result    
1.02 The actions to follow The expected result    
1.03 The actions to follow The expected result    


APPENDIX A: QUOTE & DOCUMENT HISTORY

Warning Warning: Unknown costs for client/year (TEST/2019)
Cost Details
Activity Estimate
No. of Days		 No. of Days Rate per Day (£) Cost (£ Exc. VAT)
Requirements 0.00 0.00 0 £0.00
Change Request Evaluation 0.00 0.00 0 £0.00
Functional Specification 0.00 0.00 0 £0.00
Technical Specification 0.00 0.00 0 £0.00
Development 0.00 0.00 0 £0.00
Testing and Release 0.00 0.00 0 £0.00
Implementation 0.00 0.00 0 £0.00
Project Management 0.00 0.00 0 £0.00
 
TOTAL 0.00 0.00   £0.00
Estimate excludes training, release to live and go live support.

References

Ref NoDocument Title & IDVersionDate
1Reference10.101/01/2011


Glossary

Term Definition
EPOD Electronic Proof of Delivery. The OBS EPOD system is CALIDUS ePOD.
CALIDUS eSERV The OBS mobile system to complete Service functionality in the field. This is part of the CALIDUS ePOD system.
PDA The mobile device on which the C-ePOD system will run in the field. This can be a Phone, EDA or industrial PDA, running Android.
DAL Data Access Layer. A mechanism for accessing data by the system that is removed from the application, allowing for simplified access and providing protection to the data, as only approved DAL methods can be used to modify it.
GPS Global Positioning System. A mechanism of retrieving accurate positioning information in the form of Latitude and Longitude (Lat-Long) co-ordinates from a device.
GPRS, 3G, HSDPA, Data Service All terms referring to mobile device network connectivity, and the speed at which the device connects to the internet.


Authorised By


Rev1
OBS Project Manager
_____________________________

Rev2
Customer Representative
_____________________________
Retrieved from ‘https://calidusassist.adcservices.apteancloud.com/calidus-assist/OBS/index.php?title=TEST&oldid=6913’