Date | July 31st, 2012 |
Day | Tuesday |
Time | 4:00 PM IST |
Dial-in Access Numbers | |
Mumbai | Primary Access:+91 22 3065 0539 Secondary Access:+91 22 6629 0539 |
Hexaware Participants | Atul Nishar– Chairman P. R. Chandrasekar – Vice Chairman & CEO R. V. Ramanan – Executive Director & Head – Global Delivery Prateek Aggarwal – Chief Financial Officer Deependra Chumble– Chief People Officer Sreenivas V– Chief Strategy Officer |
Wednesday, 25 July 2012
Earnings Conference Call on Tuesday, July 31st 2012 at 4.00 pm IST
Friday, 8 June 2012
Quality Assurance and Testing Services: Strategy of Oracle BI Testing
1. Testing in Levels: In a typical OBIEE project, it is advisable to test in multiple areas rather than attempting to test everything at once.
a) The first set of tests can verify the accuracy of the column to column transport of the data between the source and target. This verification is typically done using SQL statements on the source and target databases.
b) The next step is to verify the accuracy of the repository (the .RPD file.) These tests will include testing with appropriate dimensional filters on the metrics and the formula used to compute those metrics. Testers can build two sets of comparable queries within the repository interface.
c) The next step in testing will be to verify the dashboard / reports against comparable queries on repository metrics. In these tests, testers verify dashboard charts / reports against corresponding results from queries they execute on metrics of the repository.
d) Finally, the functional interface tests will cover tests to verify the lookups, performance, ease of use, look and feel etc.
The first three types of tests are performed by testers who can create simple SQL statements.
Structure and organization of test cases:
The choices on test cases naming convention and structure can help organize the test artifacts better and aid a great deal in implementing the overall testing strategy.
For example: If the test cases are grouped based on the nature of the tests, like, source to target verification, RPD metrics tests, functional, security, performance and usability, it would be easier to pick and choose the tests based on the testing context and tester capabilities.
1. User acceptance criteria:
Users typically have an existing legacy mechanism to verify if what is displayed in the new solution makes sense. Testers should dig into this and understand how the end users built the project acceptance criteria. Testers should challenge the assumptions made by the business community in deriving the acceptance criteria. This activity helps get an end user perspective built into the testing efforts from early on.
2. Validating Master Detail Report:
Master Details linking of views allows you to establish a relationship between two or more views such that one view, called the master view, will drive data changes in one or more other views, called detail views.
3. Time series functions validation: Time series functions provide the ability to compare business performance with previous time periods, allowing you to analyze data that spans multiple time periods.
Time series functions enable comparisons between current sales and sales a year ago, a month ago, and so on.
a. Ago: With ago function we can compare period to period
b. To date: Time series functions enable comparisons between current sales and sales a year ago, a month ago, and so on.
c. Period rolling: The PERIODROLLING function does not have a time series grain; instead, you specify a start and end period in the function.
4. Oracle bi-publisher validation: Oracle BI Publisher known as XML Publisher offers efficient scalable reporting solution available for complex, distributed environments. It provides a central architecture for generation and delivering information to employees', customer and business partners both security and in the right format.
Thursday, 7 June 2012
Quality Assurance And Testing Services: OBIEE Validations
Source to target validation: Here source is represented by metadata repository and Target represents OBIEE Reports & Dashboards, BI Publishers.
1. Presentation layer object validation:
This is the layer of the logical business model that is accessible for the client through the structure query Language better known as the logical SQL. The presentation is the appropriate layer to set user permissions and to validate user permissions to reports.
2. Categorizing the metrics:
It is important to classify the metrics from multiple perspectives such as, their frequency of use, potential performance impacts, and complexity of calculations involved. Such a classification helps drive priority of testing
3. Dashboard charts and filters criteria:
User interface testing should encompass tests with multiple options in the available filter criteria. OBIEE gives enough drilldown features to verify the underlying data on the clickable components of the charts. Test cases written should be detailed enough to verify data aggregated at various layers.
4. Filter Validation
. Validate the entire filters which are available on report. Example refers below report and its filter
. Example: For Performance Measure filter- Validate filter contents against report requirement and database
Filter types:
Local filters: Filtering the records in the report level.
Global filters: Filtering the records based on user selection in Dashboard.
Dashboard Validation:
When a user selects certain request that need to display the exact results in the dashboard.
5. Data level security:
Data level security validation means user will be able to see only particular data for the given permission
Example: Both the Eastern and Western region Sales Managers will be seeing the same reports but the Data visible to them in the reports will be Eastern and Western region Sales data respectively.
Object Level security: Need to validate whether the particular user is able to access the particular dashboard or folder etc.
Example: For example, users in a particular department can view only the subject areas that belong to their department.
6. Bursting the reports:
Bursting the reports means distributing the reports based on the regions.
Example: If there are 4 regional reports, validate to burst the reports (based on East, West, South, North regions).
7. Buzz Matrix validation:
Need to validate the alerts in the Dashboard.
Example: We are running stock market and CEO is very much interested to know today's business weather, has it reached a certain level that which he expects compared to the last week. If the level has reached to a certain level in Dashboard Buzz (Alert), it should raise an alert saying that it has reached the level in such a way the buzz matrix validates.
Wednesday, 25 May 2011
PHP Web Development Partner or PHP Vendor Selection: What you should know!
Thursday, 19 May 2011
Adobe Flash Builder 4.5 for PHP released for building Cross Platform Applications


Both Flash Builder and Zend Studio have been built on the Eclipse platform, so you will be able to build Flex and PHP side-by-side.
To check it out or know more about it, visit Zend.com's product page
Thursday, 24 March 2011
Team Development Concepts with Zend Studio for Eclipse Webinar Resources Released
The webinar introduced the Zend Studio 8 for Eclipse environment to the participants and walked them through the key Zend concepts & features including Views, Perspectives and Workspaces. In the webinar, Peter went on to explain how Zend Studio 8 supports team collaboration including Code Revision and development processes. Through the Webinar, we show how Zend Studio for Eclipse and PHP is the preferred option for building enterprise applications.
The video of the whole session can be seen below:
(Team Development Concepts with Zend Studio for Eclipse from OSSCube on Vimeo)
The slide deck from the webinar can be read below:
(View more presentations from OSSCube LLC A Global Open Source Enterprise for Open Source Solutions)