CSC 4332 Final correctly answered to
pass graded A+
What are the steps in software testing? - correct answer ✔✔The first steps in software testing is
looking at our specifications. After looking at our specifications we can generate our partitions
and boundaries. We can then generate different test cases.
Next we can go ahead and write our tests. We will run these and they will fail. After this we can
implement our code until our tests passes. We made need to refactor our code if we find more
test cases or want better implementation.
After this we can move onto our structural testing. We can look at our source doe and identify
the non covered parts from testing, we can use code coverage to achieve this. We can then
implement more tests for this.
After this we can implement mutation testing, where we can use a library to implement a bug
into our code and run the test suite, we should ensure that our existing test could detect the
presence of our new bug. If not, we can working on fixing this.
All of these testing steps are iterative and continuous, so after doing one of these steps we may
need to go back and do another.
Where do we get test cases from? - correct answer ✔✔We get our test cases from identifying
partitions and boundaries that we generate from the requirements from our system. These
partitions and boundaries give us different inputs and outputs that produce different code
behavior, which is where we can generate our test cases from.
Additionally after, we can get more test cases by looking at our code coverage to see any code
that is not tested and implement tests for this code behavior.
, How does software testing fit into software engineering? - correct answer ✔✔Software testing
serves as a form of verification for software. It gives us assurance that components act as they
were designed to do so.
Software testing also reduces bugs in our software. Reducing these bugs in our software helps
save costs because bugs are expensive and can cause lost reputation.
In conclusion, software is performed at different stages in the software testing development
cycle and a necessary part of generating good software in software engineering.
Where do we draw the lines to stop testing? - correct answer ✔✔We can draw lines to stop
testing by looking at our requirements.
Some external applications may not be able to be tested because of slow speed, so we can use
mocks to have a clear thing to be tested.
Some things are less important than others, and may not need to be tested.
Sometimes there are too many different things to test. For example a linux kernal may have 300
boolean flags, it is not applicable to do 2^300 tests for this linux kernel, so we can look at the
actual use cases for this kernel to generate test cases.
When should we apply specification testing? - correct answer ✔✔We should use specification
testing when we have well defined requirements and documentation
What is specification testing and what does it entail? - correct answer ✔✔Specification testing
is looking at the specification documentation and deriving a test suite.
pass graded A+
What are the steps in software testing? - correct answer ✔✔The first steps in software testing is
looking at our specifications. After looking at our specifications we can generate our partitions
and boundaries. We can then generate different test cases.
Next we can go ahead and write our tests. We will run these and they will fail. After this we can
implement our code until our tests passes. We made need to refactor our code if we find more
test cases or want better implementation.
After this we can move onto our structural testing. We can look at our source doe and identify
the non covered parts from testing, we can use code coverage to achieve this. We can then
implement more tests for this.
After this we can implement mutation testing, where we can use a library to implement a bug
into our code and run the test suite, we should ensure that our existing test could detect the
presence of our new bug. If not, we can working on fixing this.
All of these testing steps are iterative and continuous, so after doing one of these steps we may
need to go back and do another.
Where do we get test cases from? - correct answer ✔✔We get our test cases from identifying
partitions and boundaries that we generate from the requirements from our system. These
partitions and boundaries give us different inputs and outputs that produce different code
behavior, which is where we can generate our test cases from.
Additionally after, we can get more test cases by looking at our code coverage to see any code
that is not tested and implement tests for this code behavior.
, How does software testing fit into software engineering? - correct answer ✔✔Software testing
serves as a form of verification for software. It gives us assurance that components act as they
were designed to do so.
Software testing also reduces bugs in our software. Reducing these bugs in our software helps
save costs because bugs are expensive and can cause lost reputation.
In conclusion, software is performed at different stages in the software testing development
cycle and a necessary part of generating good software in software engineering.
Where do we draw the lines to stop testing? - correct answer ✔✔We can draw lines to stop
testing by looking at our requirements.
Some external applications may not be able to be tested because of slow speed, so we can use
mocks to have a clear thing to be tested.
Some things are less important than others, and may not need to be tested.
Sometimes there are too many different things to test. For example a linux kernal may have 300
boolean flags, it is not applicable to do 2^300 tests for this linux kernel, so we can look at the
actual use cases for this kernel to generate test cases.
When should we apply specification testing? - correct answer ✔✔We should use specification
testing when we have well defined requirements and documentation
What is specification testing and what does it entail? - correct answer ✔✔Specification testing
is looking at the specification documentation and deriving a test suite.
