bonfire; warm, bright, a bustle of comforting assumtion of software developemnt ....Testing is exploration of darkness....

On top of all typical marketing language and beyond the typical SDLC, either it be a SAP implementation or standard IT delivery, one of the assumption is being applied that solutions is going to work as expected but to prove it does works or not - there is always need for an intelligent testing & when we are talking about finance product testing – I don’t think a traditional testing methodology works well…

Foundation finance testing practice, that are rock in the soil that protects efforts against harshness of unexpected) -  

Other than Why? What? & How to test, require destructive testing activities, a deeper level of understanding of the “banking products accounting principals” starting from a order / contract origination to its life cycle events and test conditions surrounding to normal to abnormal life cycle and above all understanding of the data transformation, enrichment rules that system coverts into an accounting  - be it thick  or thin ledger a/c event -  transactions composed of intricate and highly ramified GL transactions help to discover events or finance requirements during the realization phase ---

How the tests should be carried out also require strong planning of each activity –As well said..“Software application implementation is a cozy bonfire; warm, bright, a bustle of comforting concrete activity. But beyond the flames is an immense zone of darkness. Testing is the exploration of this darkness.” - Extracted Software Maintenance technology magazine.

 business architect or dedicated integration lead is critical for an integrated system but someone with a brave accountancy mind tester can uncovering underlying defects or gap in requirements that could be impacting overall system in real life – as in testing language, it is said, the objective of any tester should be to try his best to crack the application feature /code. This might be seen as a destructive activity but it worth to spend money   …

Even though there's no denying the fact that Construction/Coding is a very significant phase in the life cycle of any application but same time to Reduce Costly Errors in future, destruction can also be performed –

 Some time complexity is due to several factors, some of these being: the high level of coordination needed to ensure that all accounting consequence data inputs are available or identified, generated, and managed through test life cycle…. Time is saved when experts performing the activity – both technical as well as business, business can identify what need and in what way will it be used using application however deliberately intense or thorough testing to determine the stability of the system  -It involves testing beyond normal operational functionality, to confirm intended specifications are being met; to determine modes of failure (how exactly a system may fail), and to test stable operation of a part or system outside standard usage e.g.  Posting of the wrong amount, omitting a posting, posting in the wrong area or posting more then once for in the given period – simulating source systems behaviours or applying test to thick ledger areas that may impact asset, liabilities or equity with retain earning before preparation of net income - cash flow statements drive from the finance statement so  either direct or indirect methods, test closing entries on period-end and leave one side of the balance open so the impact of the imbalanced figure from source to suspense account in GL is tested or error discovered - Prepare reverse entries deliberately simulating the discrepancies of accountancy --

It has transcended to an age of modern-technological level. With that, the demand for a more efficient system of managing finances and finding a better means of exchanging data are at an all time high, I remember a roll out of a multi million software product to market, which was like a story of Toyota Car -recalling 7m cars worldwide because of minor fault –

Software (SAP ECC or BA) it handle all of the arduous accounting work but need robust config and exception management. Finance applications focus on looking for ways on how to develop profitable business hence portfolio management testing where stress tests in payment, finance for current and future settlement is critical can also be the aim of testing.

SAP BA has full feature of management, cost and finance accountancy therefore what is being developed/ customised require testing in one go  of the implementation.. The end-aim of the system is meet finance requirement which is meet the cash flow in and out assessment on given day or period  - Strategic vision can help to deliver but ground reality is often unpredicted.. Product accounting system (SGL) need knowledge from basic journal entry of the finance conditions to bank book value to GL derivation to aggregation based on the IFRS – Fair valuation or reconciliation - all  can be tested

I believe Business process flow is always same for all accounting/ finance reports; it has been same in the industry for ages but the way of collecting, analyzing, summarizing and evaluating has changed and facilitated with applications – either it be item of debit or credit – it has not changes but the identification, registration, calculation and classification of transactions / events in a cognizable manner has forced to change because of finance meltdown (IAS/ IFRS,GAAP, MTM standards etc…..

Learning Is a Treasure That Will Follow Its Owner everywhere...A good teacher is like a candle - it consumes itself to light the way for others.