IGCSE Chapter 7 System life cycle Development, Section Development and Testing
- 1. Development and Testing 7.3 Analysis-> Design-> Development and Testing-> Implementation->Document->Evaluation Chapter 7
- 2. What is Testing? • Once the Designing stage is Completed its time for Testing before implementation or releasing it to usage
- 3. Testing after Designing Testing can be differ according to the testing item or object! Ex:- Software Testing Front end, backend, Middleware Hardwater Testing Sensors, Stability, Capability, efficiency
- 4. Hardware related Robot Testing Check this video https://youtu.be/dtyf91zauBk
- 5. Testing in Software Development • Frontend (Designs) • Input types (Using Forms, Mic, Sensors, Camera Ext) • Input Data Validation • Output Data Validation • Middle where (Functions, Commands ext. ) • Scalability of codes- Expandable • Flexibility of function – for accurate usage future development • Efficiency • Backend(Database) • File Structure- (Relational/NoSQL) • Length of each field and Types • Primary Key, Unique identifier • Relationship- Table Links
- 6. Testing System Designs 1. Data Structure: Ensure efficient data organization for quick retrieval and manipulation, considering factors like complexity, memory usage, and performance. 2. File Structure: Organize files logically and hierarchically for easy navigation, maintenance, and scalability. 3. Input Formats: Define clear specifications for input data formats to ensure consistency, compatibility, and ease of processing. 4. Output Format: Design output formats that are structured, informative, and user-friendly, facilitating easy interpretation and analysis of results. 5. Validation Routine: Implement robust validation routines to verify input data integrity, accuracy, and compliance with predefined standards or constraints, enhancing system reliability and data quality.
- 7. How the software system develop by developers • Software developed based on Modular form • Each module can give different feature and solution • Each module develop by different developers or Team • Some part of Software developer could not understand other sections • After all the modules completed its time for test it • Its for improve input and output There for each module must be configured properly and must be involved into testing process
- 9. Test Plan, Test Data and Live Data • After determining testing strategies test plan should be initiate • A list of all the test • What date is to be used to test • Type of testing(normal, abnormal or extreme) • What live data to test currently • Expected outcome or output • Data accuracy
- 10. Normal, Abnormal, Extreme • Normal • Valid data • Abnormal • Outside the limit • Less than 1( possible data can try 0,-1,-15) • Grater then 12 ( 32,45 ext.) • Letters non numeric • No integer ext. • Extreme • Rang of data to test acceptable border limit (0-50 means testing with 0 and 50)
- 11. Test Result • After testing system all the resting result should be in a report for decision making • If the expected output is not exist with the report that particular module need to be redeveloped of fix by developers again
- 12. Example of Testing plan
- 13. Its time to Exercise Page Number 184