Coding and Testing For BCA & MCA
Coding For BCA
Coding :- The coding is the process of transforming the design of a system into a computer language format. This coding phase of software development is concerned with software translating design specification into the source code. It is necessary to write source code & internal documentation so that conformance of the code to its specification can be easily verified.
Coding is done by the coder or programmers who are independent people than the designer. The goal is not to reduce the effort and cost of the coding phase, but to cut to the cost of a later stage. The cost of testing and maintenance can be significantly reduced with efficient coding.
# Code Review :-
Code Review is a systematic examination, which can find and remove the vulnerabilities in the code such as memory leaks and buffer overflows.
◼ Technical reviews are well documented and use a well-defined defect detection process that includes peers and technical experts.
◼ It is ideally led by a trained moderator, who is NOT the author.
◼ This kind of review is usually performed as a peer review without management participation.
◼ Reviewers prepare for the review meeting and prepare a review report with a list of findings.
◼ Technical reviews may be quite informal or very formal and can have a number of purposes but not limited to discussion, decision making, evaluation of alternatives, finding defects and solving technical problems.
# Testing :-
Testing is a process used to help identify the correctness, completeness and quality of developed computer software.
Executing Software in a simulated on real environment, using inputs selected somehow.
# Objectives Of Testing :-
◾ uncover as many as many as errors as possible in a given product.
◾ Demonstrate a given software matching its requirement specifications.
◾ Validate the quality of a S/W testing using the minimum cost and efforts.
◾ Generate high quality test cases, perform effective tests and issue correct and helpful problem reports.
# Errors, Bug, Fault & Failure :-
◾ Errors :- It is a human action that produces the incorrect result that produces a fault.
◾ Bug :- The Presence of error at the time of execution of the software.
◾ Fault :- State of S/W caused by an error.
◾ Failure :- Deviation of the software from its expected result. It is an event.
# Goals Of Testing :-
◼ Detect Faults
◼ Establish confidence in software
◼ Evaluate properties of software
◾ Memory usage
# Testing Methodologies :-
(1) White Box Testing
(2) Black Box Testing
# System Testing :-
◼ The system as a whole is tested to uncover requirement errors.
◼ Verifies that all system elements work properly and that overall system function and performance has been achieved.
# Types :-
◾ Alpha Testing
◾ Beta Testing
◾ Acceptance Testing
◾ Performance Testing
(1) Alpha Testing :- It is carried out by the test team within the developed organization.
(2) Beta Testing :- It is performed by the selected group of friendly customers.
(3) Acceptance Testing :- It is performed by the customer to determine whether to accept or reject the delivery of the system.
(4) Performance Testing :- It is carried out to check whether the meets the non functional requirements identified in the SRS document.
# Types Of Performance Testing :-
(1) Stress Testing
(2) Volume Testing
(3) Configuration Testing
(4) Compatibility Testing
(5) Regression Testing
(6) Recovery Testing
(7) Maintenance Testing
(8) Documentation Testing
(9) Usability Testing
# Unit Testing :-
Unit testing is a method of software testing in which the smallest parts (which we call units) of the software application are tested.
Simply put, “unit testing is a testing in which the program is broken into pieces, and each piece is tested closely.”
The main objective of this testing is to ensure that the source code of each unit of the software is correct and can be used.
Earlier adhoc tools were used to test units, but nowadays frameworks (Java Framework, .Net Framework and PHP Framework etc.) are used to test units.
Unit tests are written and performed by developers and the WHITE BOX TESTING method is used to do this.
The thing to remember here is that “unit testing takes too much time and requires a lot of patience”.
This testing is very effective as most defects are identified by its use.
Generally unit testing is done after integration testing.
# Advantages Of Unit Testing :-
1: – Through this testing, we find defects and bugs in the software only in the early stages, later it becomes very difficult to find defects and bugs.
2: -This testing makes the coding process more effective and agile (agile) so that we can add more and more features to the software.
3: -When we do unit testing, we need less manual testing. Anyway, manual testing is very boring and expensive.
4: – Through this testing, we can improve the design of the software without breaking it.
5: -When we detect bugs in advance, it saves our time and cost.
6: -This increases the efficiency of testing code and it becomes easy to maintain.
7: -An advantage of this testing is that it provides us with the updated documentation of the software.
# White Box Testing :-
The testing in which the tester has knowledge of the internal structure of the software is called white box testing. This type of testing is based on the working inside the software.
This testing is called a white box because the software it contains is like a white box for the tester inside which it can see.
In this type of testing, the tester has knowledge of programming. The major advantage of this testing is that we can detect errors at the beginning stage of software development.
This testing is also called open box testing, glass box testing and structural testing.
# Black Box Testing :-
A black box is a testing in which the tester does not have to have knowledge of the structure inside the software and the tester does not have to have knowledge of coding.
Black box testing is a testing technique in which the performance of the software under test is tested while the internal code structure of the software is not seen.
Black box testing only focuses on the input and output of the software.
For example: Suppose we have to do black box testing of the software of whats app, then we only pay attention to its input and output when we do not know the coding of its internal structure.
Black box testing is also called input-output testing. This testing is called black box testing because the software that it contains is like a black box for the tester, inside which it cannot see.
More Related Articles :-