Sunday 17 September 2017

Telerik Reporting (HTML5 Report Viewer)

HTML5 Report Viewer

The HTML5 Report Viewer is a pure HTML5/JavaScript/CSS3 jQuery-based widget that allows displaying Telerik Reporting reports in an HTML page. The layout/styling is based on pure HTML5 templates and CSS3 styles and is fully customizable. The default implementation supports mobile as well as desktop browsers. The responsive layout adapts itself to the device display for best viewing experience. Visual appearance can be customized by the Kendo UI theming mechanism.






Report Preview Area

The Report Preview area provides the placeholder for the rendered report. All commands provided by the toolbar operate on the report currently shown in this area.
It has built-in support for end-user interactions such as drill-down and drill-through, navigation to bookmarks in the report and external URLs.


Report Parameters

The parameters pane provides intuitive UI for user input.
When at least one report parameter has its Visible property turned on a parameter area is shown as part of the report viewer. This helps the report developer to easily provide input method for the end users. Based on the type of the parameters, a suitable editor UI is created. Parameter layout on the parameter area is formatted automatically. The order is determined by the order in which parameters appear in the ReportParameters collection. The end user can enter or select values in the editors.
When at least one visible report parameter has AutoRefresh property turned off a Preview button appears. In this case to preview the report, the end user should click the Preview button. If all parameters have default values, the report runs automatically on first view. You can show or hide the parameters area from the Parameters button in the report viewer’s toolbar.

Document Map

The document map pane provides a set of navigational links to report items in a rendered report. When you view a report that has a document map, a separate side pane appears next to the report preview area. A user can click a link in the document map to jump to the report page that displays the corresponding item. Report sections and groups are arranged in the hierarchy of links. Clicking items in the document map refreshes the report preview and displays the area of the report that corresponds to the item in the document map.
To add links to the document map, you set the DocumentMapText property of the report item to text that you create or to an expression that evaluates to the text that you want display in the document map.

How it works

The HTML5 Report Viewer is a composite of Telerik Kendo Ui widgets, which template consists of three files: HTML (UI), CSS (styles), JS (functionality). The viewer can be styles and customized with standard JavaScript, CSS and custom HTML. For more details refer to HTML5 Report Viewer Customizing articles.
The purpose of the HTML5 Report Viewer is to display Telerik Reports and allow the user to interact with them. Reports are processed and rendered on the server where Telerik Reporting engine and Reporting REST service run. Reports and their resources are handled and delivered to the viewer through the Reporting REST service.
The HTML5 Report Viewer's content is rendered in DIV elements. The report in the viewer is rendered through the HTML rendering mechanism based on the Design Considerations for HTML Rendering.

For more detail check these links



http://www.telerik.com/products/reporting.aspx
http://docs.telerik.com/reporting/html5-report-viewer




Friday 7 August 2015

Ecommerce website testing checklist

E commerce website testing checklist








Functionality Tests 
1. Test Home page.
2. Test Featured Products page.
3. Test Special Offers page.
4. Test About Us page.
5. Test Shipping Information page.
6. Test Returns Policy page.
7. Test Terms page.
8. Test Privacy Policy page

Product Categories 
1. Test any filters such as product filters, colours, sizes, types of product, etc.
2. Test any ability to sort products by name, price, size, etc.
3. Test add to shortlist or wish list facility.
4. Test add to basket function

Product Detail Pages 
1. Check product title.
2. Check product description.
3. Check product images
4. Test enlarge image function.
5. Test 360 degree view of products function.
6. Check related products.
7. Check any further product information, colours, sizes, options and extras.
8. Test add to basket function.

Product Search 
1. Keyword search ­ see separate site search test plan

Shopping Basket
1. Add products to basket.
2. Remove product from basket.
3. Change quantities.
4. Select delivery option.
5. Check VAT and delivery costs add up correctly.

Pay Now 
1. Move into checkout process.


Checkout and Payment Systems 

Tests Checkout Process
1. Test checkout process.
2. Final amount to pay – make sure that this value is correct, after the price of the products, VAT, delivery and any other charges.
3. Test making changes to the products being ordered, changing delivery options, etc. and make sure that the final amount updates correctly.

Payments 
1. Carry out a test payment using each payment method that you are offering.
2. Place Paypal payment.
3. Place Visa payment.
4. Place Visa Debit payment.
5. Place Visa Electron payment.
6. Place Mastercard payment.
7. Place Amex payment.
8. Place false payment.
9. Test cancelling order.
10. Check that confirmation emails are sent correctly when a payment is made.
11. Make sure that you can refund a payment.
12. Any refund confirmation emails are sent to the recipient successfully.


Browser Compatibility Tests Test Functionality In Following Browsers 
1. Internet Explorer 8.
2. Internet Explorer 9.
3. Internet Explorer 10.
4. Chrome (latest version).
5. Firefox (latest version).
6. Safari (latest version).



Mobile Device Compatibility Tests 

1. Apple iPhone.
2. Apple iPad.
3. Android Smartphone.
4. Android Tablet.
5. Blackberry.
6. Windows Phone


Performance Tests Performance 

1. Performance test of home page.
2. Performance test of product page

Accessibility Tests 
1. Test your website against WCAG 2.0 guidelines.
2. Try browsing your website with a screen reader and/or text browser.
3. Try browsing your website without a mouse, I.e. with just your keyboard.

Social Tests 
1. Social buttons, icons or links are in place and work correctly.
2. Any sharing buttons should also be configured correctly.


Thank you for using this website testing checklist................... 

Sunday 18 September 2011

penetrtion testing


penetration test, occasionally pentest, is a method of evaluating the security of a computer system or network by simulating an attack from malicious outsiders (who do not have an authorized means of accessing the organization's systems) and malicious insiders (who have some level of authorized access). The process involves an active analysis of the system for any potential vulnerabilities that could result from poor or improper system configuration, both known and unknown hardware or software flaws, or operational weaknesses in process or technical countermeasures. This analysis is carried out from the position of a potential attacker and can involve active exploitation of security vulnerabilities.
Security issues uncovered through the penetration test are presented to the system's owner. Effective penetration tests will couple this information with an accurate assessment of the potential impacts to the organization and outline a range of technical and procedural countermeasures to reduce risks.
Penetration tests are valuable for several reasons:
  1. Determining the feasibility of a particular set of attack vectors
  2. Identifying higher-risk vulnerabilities that result from a combination of lower-risk vulnerabilities exploited in a particular sequence
  3. Identifying vulnerabilities that may be difficult or impossible to detect with automated network or application vulnerability scanning software
  4. Assessing the magnitude of potential business and operational impacts of successful attacks
  5. Testing the ability of network defenders to successfully detect and respond to the attacks
  6. Providing evidence to support increased investments in security personnel and technology