1/14
Looks like no tags are added yet.
Name | Mastery | Learn | Test | Matching | Spaced |
---|
No study sessions yet.
Syntax Errors
Errors within the code causing program failure
Logic Errors
Errors altering program outcome, not causing failure
Suitable Test Data
Data types for testing program functionality
Normal Data
Accepted data without errors
Invalid Data
Correct data type but does not meet requirements
Erroneous Data
Data not of correct data type
Boundary Data
Data at the edge of specified range
Terminal Testing
takes place once the program has been completed. It tests the whole program at the end of its development
Iterative Testing
Testing sections of code throughout development to ensure it runs correctly throughout the code
Sub-program
Block of code with an identifier called when needed.
Using sub-programs helps in organizing and maintaining code efficiently.
Naming Conventions
General rules for creating identifiers in programming languages
Eg:
Separate words in identifiers using an underscore
ā¢ Write constants that will be remain constant throughout the program in capital letters
ā¢ When creating classes, start each word with a capital letter
ā¢ When creating functions use lowercase letters and separate with an underscore
Maintainability
Ease of future program maintenance through structure and layout
Examples:
Comments
Indentation
Sub programs
Naming Conventions
Indentation
Forced in some languages like Python for program functionality
Input Sanitisation
Cleaning up user input for suitable processing
Validation
Checks if user input is in correct format, not correctness