Unit Testing - Reading Assignment

[PaulS96]

1. What is Unit Testing?
   Individual units of code are tested if they are fit for deployment.
2. Refactoring means that you change and (hopefully) improve the internal structure of the code without changing the behaviour of the code. For example, developers may change a piece of code in order to make the code run faster but still perform the same task. Why is unit testing important for refactoring?
   To test the individual function which has been refactored instead of testing everything. If an error occurs the source of the error is more easily localized.
3. How does Unit Testing help the bottom-up testing approach?
   First every part of a program is tested before the program as a whole is tested. this makes integration testing less complicated.

[CipherGrind]

1. What is Unit Testing?
   individual units of source code are tested to determine if they are fit for use. Each test case is usually independent from others.

2. Refactoring means that you change and (hopefully) improve the internal structure of the code without changing the behaviour of the code. For example, developers may change a piece of code in order to make the code run faster but still perform the same task. Why is unit testing important for refactoring?
   This technique motivates programmers to create decoupled and cohesive code bodies which is good practice. Design patterns, unit testing, and refactoring often work together to produce the best solution.

3. How does Unit Testing help the bottom-up testing approach?
   By testing the parts of a program first and then testing the sum of its parts, integration testing becomes much easier.

[MrGanD]

1. What is Unit Testing?

Unit testing is a method by which individual units of source code are tested to determine if they are fit for use.

2. Refactoring means that you change and (hopefully) improve the internal structure of the code without changing the behaviour of the code. For example, developers may change a piece of code in order to make the code run faster but still perform the same task. Why is unit testing important for refactoring?

Unit testing allows the programmer to refactor code at a later date, and make sure the module still works correctly. The procedure is to write test cases for all functions and methods so that whenever a change causes a fault, it can be quickly identified and fixed.

3. How does Unit Testing help the bottom-up testing approach?

By testing the parts (units) of a program first and then testing the sum of its parts, integration testing becomes much easier.

[Vendi]

@ivan

Welcome to the discussion about this reading assignment.

Leave your answers to the questions below in this thread. If you have any questions or you want to discuss something connected to the assignment feel free to do it in this thread as well, but please everything to the topic.

1. What is Unit Testing?
2. Refactoring means that you change and (hopefully) improve the internal structure of the code without changing the behaviour of the code. For example, developers may change a piece of code in order to make the code run faster but still perform the same task. Why is unit testing important for refactoring?
3. How does Unit Testing help the bottom-up testing approach?

1. In most programming languages, that is a function, a subroutine, a method or property which you test in your code as smaller parts to make sure they are working propery. Unit Testing is done during the development (coding phase) of an application by the developers

2. You want to make sure the code runs smoothly, If you test it after changing the structure with Refactoring, it can be a pain to find the issues after.

3. Using bottom up approach with unit testing can be beneficial because you can put the units of the codes and test them togheter to make sure everything works properly.

[zlr1984]

1. What is Unit Testing?

Unit testing is a method by which individual units of source code are tested to determine if they are fit for use.

2. Refactoring means that you change and (hopefully) improve the internal structure of the code without changing the behaviour of the code. For example, developers may change a piece of code in order to make the code run faster but still perform the same task. Why is unit testing important for refactoring?

Unit testing allows the programmer to refactor code at a later date.

3. How does Unit Testing help the bottom-up testing approach?

Unit testing can simlipify the task, identify the single parts or functions not working.

[arminoovic]

1. Unit Testing is about ‘testing’ parts/fractions of the (source-) code of software applications.
2. Unit Testing in the context of ‘refactoring’ ensures that potential ‘bugs’ can be identified more quickly.
3. Unit Testing ensures that single software components are working properly, which will support the process of integration testing, as the software exactly knows about the specific functionalities within the sub-components.

[aldrin]

1. What is Unit Testing?

individual units of test where parts of the code are tested and fit to use .

2. Refactoring means that you change and (hopefully) improve the internal structure of the code without changing the behaviour of the code. For example, developers may change a piece of code in order to make the code run faster but still perform the same task. Why is unit testing important for refactoring?

to validate if the changes done in the code are good without affecting the behavior of other units.

3. How does Unit Testing help the bottom-up testing approach?

testing the parts of the program first; then testing the whole sume of all the parts would be easier.

[versus]

1. unit testing is a method by which individual units of source code are tested to determine if they are fit for use.
2. To make sure the code still works correctly in the entire app and to facilate futur changes
3. By testing the parts of a program first and then testing the sum of its parts, integration testing becomes much easier

[gmfaraaz]

A1. It is a process of testing a single code component to ensure the functionality works and is fit to combine with full code base.
A2. To avoid the possibility of introducing new bugs and breaking the functionality
A3. It makes it easy to identify new bugs easily and maintains good quality integration

[ARK]

1. What is Unit Testing?
   testing sections of code
2. Refactoring means that you change and (hopefully) improve the internal structure of the code without changing the behaviour of the code. For example, developers may change a piece of code in order to make the code run faster but still perform the same task. Why is unit testing important for refactoring?
   After such a change, you can find out if there is a bug or unwanted result in sections of the code
3. **How does Unit Testing help the bottom-up testing approach?**You can test the entire program. But you can also do smaller tests on the smaller sections and can find bugs, etc., in the smaller locations or sections where they are happening.

[Xabier22]

1. Unit testing is writing reusable code that tests different components of an application separately.
2. Thanks to unit testing we can refactor code and instantly know if it works the same.
3. With unit testing we can test how components work on their own and also how they affect the program when combining them with other components

[Mohammed_Al_Arab]

1. Unit testing is verifying that different parts of a code function properly and deliver the desired outcome.
2. Unit testing ensures that a code can be tested after refactoring to ensure proper execution.
3. Unit testing helps in the bottom-up approach because it tests the building blocks of a larger set of code. This can help identify more specifically where an error is coming from instead of having multiple options.

[hmpbkj]

1. What is Unit Testing?

a method by which individual units of source code are tested to determine if they are fit for use.

2. Refactoring means that you change and (hopefully) improve the internal structure of the code without changing the behaviour of the code. For example, developers may change a piece of code in order to make the code run faster but still perform the same task. Why is unit testing important for refactoring?

make sure the module still works correctly (e.g., in regression testing). The procedure is to write test cases for all functions and methods so that whenever a change causes a fault, it can be quickly identified and fixed.

3. How does Unit Testing help the bottom-up testing approach?

By testing the parts of a program first and then testing the sum of its parts, integration testing becomes much easier.

[Madlearner]

1. What is Unit Testing?
   Is a test to determine if the software built is fit for deployement and use.
2. Refactoring means that you change and (hopefully) improve the internal structure of the code without changing the behaviour of the code. For example, developers may change a piece of code in order to make the code run faster but still perform the same task. Why is unit testing important for refactoring?
   To detect the fault faster and correct the code.
3. How does Unit Testing help the bottom-up testing approach?
   Performing a test on the parts of a program first and then testing the sum of its parts.

[GrettaIsBack]

1- Unit testing means to test smaller, isolated components of you application/software
2- When refactoring, you need to make sure all the changed, added os removed pieces of your application will still work as intended after an upgrade for ie. And when you have unit testing, you can check for each part and if there’s bugs for ie btw a component of other (such as a function, or a nother piece of code, variables, etc) it’s easier do identify where the problem is.
That helps to create automated testing as well.
3- Since unit is the smaller piece possible to be tested, comes handy the model of bottom up testing so you can take smaller pieces and going up in the chain of related components and interactions of the bigger picture of your software.

[SAINTPATRICK]

1.Unit Testing is a method by which individual units of source code are tested to determine if they are fit for use. A unit is the smallest testable part of an application. In procedural programming a unit may be an individual function or procedure. Unit tests are created by programmers or occasionally by white box testers. Each test case is independent from the others and substitutes like method stubs, mock objects, fakes and test harnesses can be used to assist testing a module in isolation.

2. refactoring shouldn’t affect the inputs and outputs to a given function, the unit tests can effectively determine if logic/functionality was altered.

3.By testing parts of a program first then test the sum of the parts, it makes it easier for integration testing.

[Joeyj007]

1. What is Unit Testing?
   In computer programming, unit testing is a method by which individual units of source code are tested to determine if they are fit for use.

2. Refactoring means that you change and (hopefully) improve the internal structure of the code without changing the behaviour of the code. For example, developers may change a piece of code in order to make the code run faster but still perform the same task. Why is unit testing important for refactoring?
   Unit testing allows the programmer to refactor code at a later date (e.g., in regression testing). The procedure is to write test cases for all functions and methods so that whenever a change causes a fault, it can be quickly identified and fixed.

3. How does Unit Testing help the bottom-up testing approach?
   Unit testing may reduce uncertainty in the units themselves and can be used in a bottom-up testing style approach. By testing the parts of a program first and then testing the sum of its parts, integration testing becomes much easier.

[paradox]

1. A method by which individual units of source code are tested to determine if they are fit for use
2. You could break something by refactoring and you need to test to make sure you didn’t
3. By testing units of the code first, it eliminates bugs that could show up in integration testing

[Alexlane8]

1. What is Unit Testing?

A method by which individual units of source code are tested to determine if they are fit for use. A unit is the smallest testable part of an application.

Unit tests are typically written and run by software developers to ensure that code meets its design and behaves as intended. Its implementation can vary from being very manual (pencil and paper) to being formalized as part of build automation.

2. Refactoring means that you change and (hopefully) improve the internal structure of the code without changing the behaviour of the code. For example, developers may change a piece of code in order to make the code run faster but still perform the same task. Why is unit testing important for refactoring?

Unit testing allows the programmer to refactor code at a later date, and make sure the module still works correctly (e.g., in regression testing). The procedure is to write test cases for all functions and methods so that whenever a change causes a fault, it can be quickly identified and fixed.

Readily-available unit tests make it easy for the programmer to check whether a piece of code is still working properly.

3. How does Unit Testing help the bottom-up testing approach?

Unit testing may reduce uncertainty in the units themselves and can be used in a bottom-up testing style approach. By testing the parts of a program first and then testing the sum of its parts, integration testing becomes much easier.

[marsrvr]

1.) What is unit testing?
Testing for one small function within your project.

2.) “Refactoring” means that you change and (hopefully) improve the internal structure of the code without changing the behavior of the code. For example developers may change a piece of code in order to make the code run faster but still perform the same task. Why is unit testing important for refactoring?
Unit testing, preferably automated, would be the only means of proving that no harm was done in the refactoring in any small code unit. Hopefully there’s also system-level integration tests running in an automated fashion to test aggregate subsystems and assembly interfaces.

3.) How does Unit Testing help the bottom-up testing approach?
Unit testing is half of Test-Driven-Design, or later “behavior-driven design” (depending on how the test cases are defined), which allows for each lower-level function within the project to be individually tested. This is followed by integration tests at each level of aggregation within the project.