= Excel Integration - To Do List =

 * [[ExcelIntegration|Back]]

<<TableOfContents>>

= Implementation and Bug Fixes =

== Bug Fixes ==

 1. '''AH''' - Diagnose errors reported by GMM
 1. '''AH''' - Implement highlighting of deleted records in ''Refresh Row''
 1. Fix display of Umlaut characters in error messages

== Implement New Functionality ==

 1. Design for document links
 1. Implement ''Preufdauer'' menu and handling of ''Delta-4'' field
 1. Implement document links for ''Grundlagen'' documents. ''tech GL'' and ''WV GL'' fields.
 1. Implement document links for ''Stellungnahmen'' and ''Pruefberichts'' documents.  ''Stn-Nr'' and ''Pruef-Nr'' fields.
 1. Implement document links for ''QA-Eklaerung'' documents

== Login/Logout/Exit ==

 1. Gracefully handle when user not logged in
    * Implement routine to catch and report not being logged in
    * All menu items that access server should be able to respond to a non-logged in error
 1. Trap Excel-Quit and ask user if unsaved records should be saved ''(design needed)''
 1. Implement login timeout
 1. Implement code that reacts correctly to auto-logout. E.g. session-timeout
    * Implement a heartbeat function to prevent session timeout?
 1. Check user roles and disallow login if certain roles not present
 1. Login in a specific contract?

== Search ==

 1. In search form implement ''Gruppe'' menu with dependency on ''Bereich'' menu ''(design needed)''
 1. Change ''New Worksheet'' checkbox to ''Clear Existing Sheet'' in ''Search'' and ''Test Cases''
 1. Implement named baskets (Design needed)
    * User can select a named basket download its contents
    * Make sure all calculate fields are readonly
 1. Mark row as ''un-savable'' if revision sequence is incomplete?

== Attributes Lists ==

 1. Separate ''Refresh Attributes'' into:
    * ''Refresh Attributes''
    * ''Refresh Users and Roles''
 1. Shorten attribute lists ''(design needed)''
    * Via server-side configuration?

== Implement Improved Revision Processing ==

 1. Reject revision ''(design needed)''
 1. Sub-revision processing ''(design needed)''

== Internals ==

 1. Implement new ''Magic Row'' fields:
    * Protocol version
    * Client software version
    * Server software version

== Internationalization ==

 1. Convert all user display text to ''Const'' strings
 1. Translate all messages ''Const''s into DE
 1. Implement tag and lookup for form text ''(design needed)''

== Final Packaging ==

 1. Set password on VBA code
 1. Get code signed with a Axpo certificate?
 1. Re-hide hidden rows/columns in header worksheet
    * Ensure that non-implemented fields are locked/greyed-out
 1. Setup field worksheet field locking (probably not)
 1. Hide internal worksheets


----

= Testing =

== Test Plan and Setup ==

 1. Write a test-plan wiki page
 1. Make sure ZK/TN/DD have suitable test environments

== Basic Tests ==

 1. Check reading and updating of all fields
    * Save values and read back
    * Check values on server
 1. Stress/performance testing
    * Searching for long lists
    * Bad input data
 1. Character sets: test with Umlaut characters
    * Test Umlauts in UTF-8 set to server
    * Test Umlauts in ISO-8859-1 set from server
    * Test Umlauts in error messages
 1. Compatibility testing
    * Excel 2003 menus
    * Excel 2003 complete functionality
 1. Search tests
    * Test all search fields
    * Test functionality of ''Bereich'' and ''Gruppe'' menus
 1. Display tests
 1. List menu tests
    * Status menus
    * User menus
    * Flag menus
 1. Editing tests
    * Delta date calculations
    * Drawing code menus
 1. Insert tests
 1. Update tests
 1. Client-side validation tests
    * Leave ''Wer'' and ''Status'' field validation for now
 1. Menu item tests
    * Check for duplicates
    * Duplicate selected
 1. Performance tests
 1. HTTPS test
 1. HTTP/HTTPS proxy test


= Testing of Specific Features =

== Search ==

 1. Search fields: Test all search fields:
    * document code
    * title
    * revision date from/to
    * external reference number
 1. Searching for more than selected the number of records
    * Ensure ''cancel/continue'' dialog functions correctly

== Display of Search Results ==

 1. Display/clearing of cell comments
 1. Search correctly merges new data with existing data
    * Make sure that if you re-arrange the order of documents in a worksheet, that search still operates correctly. E.g. check th t search is able to re ognize existing documents in the worksheet and doesn't depend on the order of documents delivered by the s rver.
 1. Display/removal of ''progress menu'' in lower left message area

== Editing ==

 1. Check for Copy and Paste problems - specifically related to ''onChange'' routine
 1. Contract and group menu changes in planning list worksheet
    * Make sure group menu updates when contract changed
    * Make sure user id menus change when contract and group changed
 1. ''Get Next Sequence Number''
 1. Generate client-side error on update/insert when drawing code not complete
 1. ''Vorabzug'' flag handling and ''RevC Revision Type'' menu handling
    * See ''[[ExcelIntegrationRequirements#GA.2BAC8-FregegebenMenu]]''
    * Test the ''onChange'' handling for ''Vorabzug'' menu and ''Rev``C'' type fields.
      * Make sure the revision code and revision type are changed and set correctly
      * Make sure the ''Vorabzug'' fields are locked/unlocked when the flag is changed
      * Make sure the ''Vorabzug'' fields are cleared when flag not set and records saved
 1. Field highlighting
    * Status colors:
      * ''gray'' - saved
      * ''yellow'' - changed
      * ''red'' - error
    * Events:
      * New record (set to yellow)
      * Re-started record (set to yellow). E.g. after restart revision sequence
      * Record changed locally (set to yellow)
      * Client-side error? (set to red)
      * Server-side error (set to red)
      * Record saved (set to white)
 1. ''New Document'' inserts after selected row
    * Should append data after last selected cell, or last row if nothing selected
 1. ''Duplicate Row'' should duplicate after the last selected row
    * And should not have problems when blank rows are selected
 1. Client-side field validation
    * Ordering/gaps in plan complete date fields
    * Ist field validation
    * Status
 1. ''Refresh All'' and ''Refresh Selected'' update the record update counts in key set area
    * Search, then make update on the server, refresh the client and ensure that the update counts are correctly updated
 1. Should ''Restart Revision Sequence'' not be allowed when applied to an unsaved record? Probably not
 1. Make sure ''Refresh Attributes'' still works
 1. Make sure that no problems occur when user changes worksheet names


= End-to-End Testing =

 1. Define scenarios
    * Client-side only
    * Client and Server interactions
 1. Functional testing
 1. Performance testing
    * Measure performance with large data sets
    * Profile code to see what is being called for each document/revision
    * Review calls to ''DoEvents''


= User Documentation =

 1. Define outline/structure for user documentation
 1. Setup wiki pages


= Internal Documentation =

 1. List of modules
 1. List of public subs/functions
 1. List of ''gotchas''
    * Blank cells in header regions, caused by use of Excel ''count2'' function
 1. Explanation of complex menu and look formulas)
 1. Convert notes/DesignNotes into Wiki
 1. Revision sequence
 1. Named ranges
 1. URLS for REST transactions
 1. XML structures
    * Returned records
    * Insert/update records

= Internals and Refactoring =

 1. Named ranges
    * Automated management
    * Function for repair/reset of named ranges in case of corruption
    * Clone worksheet
    * Document named ranges and their boundaries
 1. Make sure ''Consts'' are used for all field type names in the write-back header worksheets
 1. Change ''iRow'' to ''lRow''?
 1. Document new validation columns in header structure
 1. Document and revision (write) record structures
 1. Improved worksheet lookup/access functions (''getCellValue/Address'')
 1. Improved row selection for printing to worksheet
 1. Refactor define names to improve clarity and remove confusing near-aliases
 1. Identify all magic constants and convert to ''Consts''
 1. Improve function naming:
    * Use function names that more ''business oriented'' rather than ''technically descriptive''
 1. Review ''TODO''s in code