1. Samuvel Johnson 1286120 2 nd MCA B

2. Contents  Introduction to Real-time systems  Two main types of system  Testing real-time software  Difficulties with testing such software

3. Introduction  What is a Real-time System?  A real time system is one that “is subject to real time constraints” meaning that operations must produce a response within a given time.  Examples include:  Air traffic control systems  Medical monitoring  Weapons delivery systems  Space navigation and guidance

4. Types of Real-time System  There are two main types of real-time systems:  Hard real-time system – Requires that operations must be completed within their deadline e.g. systems in space shuttles, fight control.  Soft real-time system – Although it is emphasised that deadlines are important they are not as strict as in hard real-time systems.

5. How do we test software in real-time systems?  A strategy for testing real-time software should include:  Low-level tests – single lines of code  High-level tests – methods and functions  In order to test such software one technique might be to generate and test sequences by applying time constraints in which they must be completed.

6. The 3-stage approach to testing real time software  1. Identification of tasks  Output Testing  Performance Testing  2. Incorporation of tasks  Output Testing  Performance Testing in a real environment  3. Integration Testing

7. Difficulties with testing Real-time software  It is difficult to test a system that is running in real time due to factors such as:  Time constraints  Conventional methods are not applicable for real- time software  This can lead to…  Unpredictable outcomes

8. Summary  A real-time system is subject to time constraints  Two main types of real-time system  No single way of testing this software  Difficulties with testing such software

9. Any questions?

10. References  http://msdn.microsoft.com/en-us/library/aa459157.aspx http://msdn.microsoft.com/en-us/library/aa459157.aspx  http://en.wikipedia.org/wiki/Real-time_computing http://en.wikipedia.org/wiki/Real-time_computing  http://www.ndt.net/article/wcndt00/papers/idn235/idn23 5.htm http://www.ndt.net/article/wcndt00/papers/idn235/idn23 5.htm  http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber= 139423 http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber= 139423

11. Samuvel Johnson 1286120 2 nd MCA B

12. WEB APPLICATION TESTING  Web Testing in simple terms is checking your web application for potential bugs before its made live or before code is moved into the production environment.

13. 1. Functionality Testing : 2. Usability testing: 3.Interface Testing: 4.Database Testing: 5. Compatibility testing. 6.Performance Testing: 7. Security testing: 8.Crowd Testing:

14. 1. Functionality Testing :  Test all links in your webpages are working correctly and make sure there are no broken links. Links to be checked will include -  Outgoing links  Internal links  Anchor Links  MailTo Links

15.  Test Forms are working as expected  Test Cookies are working as expected. Test HTML and CSS Test business workflow 1. Functionality Testing :

16. 2. Usability testing:  Usability testing has now become a vital part of any web based project. It can carried out by testers like you or a small focus group similar to the target audience of the web application.  Test the site Navigation:  Test the Content:

17. 3.Interface Testing:  Three areas to be tested here are - Application, Web and Database Server  Application: Test requests are sent correctly to the Database and output at the client side is displayed correctly. Errors if any must be caught by the application and must be only shown to the administrator and not the end user.

18.  Web Server: Test Web server is handling all application requests without any service denial.  Database Server: Make sure queries sent to the database give expected results. 3.Interface Testing:

19.  Test system response when connection between the three layers (Application, Web and Database) can not be established and appropriate message is shown to the end user.  Tools that can be used: AlertFox,Ranorex 3.Interface Testing:

20. 4.Database Testing:  Test if any errors are shown while executing queries  Data Integrity is maintained while creating, updating or deleting data in database.  Check response time of queries and fine tune them if necessary.  Test data retrieved from your database is shown accurately in your web application  Tools that can be used: QTPQTP

21. 5. Compatibility testing.  Compatibility tests ensures that your web application displays correctly across different devices. This would include-  Browser Compatibility Test: Same website in different browsers will display differently. You need to test if your web application is being displayed correctly across browsers, javascript, AJAX and authentication is working fine. You may also check for Mobile Browser Compatibility.

22.  The rendering of web elements like buttons, text fields etc changes with change in Operating System. Make sure your website works fine for various combination of Operating systems such as Windows, Linux, Mac and Browsers such as Firefox, Internet Explorer, Safari etc.  Tools that can be used: NetMechanic 5. Compatibility testing.

23. 6.Performance Testing:  This will ensure your site works under all loads. Testing activities will include but not limited to -  Website application response times at different connection speeds  Load test your web application to determine its behavior under normal and peak loads  Tools that can be used: Loadrunner, JMeterLoadrunner

24. 7. Security testing:  Security testing is vital for e-commerce website that store sensitive customer information like credit cards.  Tools that can be used: Babel Enterprise, BFBTester and CROSS

25. 8.Crowd Testing:  You will select a large number of people (crowd) to execute tests which otherwise would have been executed a select group of people in the company.  Tools that can be used: People like you and me !!!.

26. THANK YOU