Software Quality and Testing

Credits To @wezlar11 Image Link 1. What is “correctness” in agile processes? Correctness is a measure to a code that targets the level in which such code meets the specified requirements. Basically it checks if the code has the desired behavior. 2. Do TDD tests do a good job testing the software? TDD is very good for testing the functionally of small parts of your code as you develop. However TDD will not be able to guarantee that your tests are well thought and enough. 3. Can we automate our tests without TDD? Yes, we can create tests after the creation of our code. These tests aren’t considered as TDD but still a way of automation. 4. Can we use TDD without automating our tests? No, the whole idea of using TDD is having the ability to automate our tests due to the fact that we don’t already have a code to test. 5. What four structures do we use for test criteria? Input domains, graphs, logic expressions, and syntax descriptions. 6. What usually prevents ...

Credits to @crissyjarvis Image Link Answer Exercise#1 (see below) from Chapter 4 Instructions: Calc currently implements one function: it adds two integers. test-driven design to add additional functionality to subtract integers, multiply two integers, and divide two integers. First create a failing test for one of the new functionalities, modify the class until the test passes, then perform any refactoring needed. Repeat until all of the required functionality has been added to your new version of Calc, and all tests pass. Remember that in TDD, the tests determine the requirements. This means you must encode decisions such as whether the division method returns an integer or a floating point number in automated tests before modifying the software. Github Link Activity

Credits to @borisworkshop Image Link In all honesty this is a very boring reading, the writing is too complex for the actual content and its meaning. The main idea is: mine software repositories to discover how teams (ought to) coordinate and communicate. For example, can we really assume that if two developers didn’t send each other an email on a particular period then they were working uncoordinated? It’s an (until recently) untested assumption, but that doesn’t seem to give much pause to the researchers in the area. I think the explosion of interest in MSR was motivated by frustration with the difficulty in doing something ’empirical’ in software engineering References: The secret life of bug's

Main Activity  package itesm.mx.activity3_aboutmyself; import android.app.Activity; import android.content.Intent; import android.support.v7.app.AppCompatActivity; import android.os.Bundle; import android.util.Log; import android.view.View; import android.widget.Button; import android.widget.EditText; import android.widget.Toast; public class MainActivity extends AppCompatActivity { private EditText input ; private Button b1 ; private static final int PERRITO_CODE = 0 ; @Override protected void onCreate(Bundle savedInstanceState) { super .onCreate(savedInstanceState); setContentView(R.layout. activity_main ); input = findViewById(R.id. editText ); b1 = findViewById(R.id. button ); } public void buttonTest(View v) { Intent intent = new Intent( this , MenuActivity. class ); //startActivity(intent); startActivityForResult(intent, PERRITO_CODE ); } } Menu Activity / Perrito Activity ...

Credits to @suika Image Link Week 4 Plan: 1. Continue doing research about how to do unit testing or some sort of testing on Android Studio. 2. If research successful do a quick test and make a blog post about it. 3. Finish Chapter 3 Exercises. 4. Each member must do a commit and push to the team's repository on GitHub of the exercises. 5. Get ready for Partial 1 Exam. Week 4 Review: 1. We talked to Guillermo Rivas who is the Mobile Apps profesor and he told us that it is possible to integrate unit testing to Android Studio with Junit since we are using Java but that he didn't know how to get that environment working. So we did some research about getting that set up and here's a very useful guide that we found: Build Local Unit Tests 2. We ended un trying to import Junit but it kept displaying an error of versioning, so we're going install again Android Studio but with an extension pack that includes Junit. 3. Those are done and there up on the team...

Q. 1 "Test Automation software is the best way to increase the effectiveness, efficiency and coverage of your software testing"(SmartBear, 2019). Testerst automate tests in an automated testing tool because is able to playback pre-recorded and predefined actions, compare the results to the expected behavior and report the success or failure of these manual tests to a test engineer. Automated tests differ from manual testing where a human being is responsible for single-handedly testing the functionality of the software in the way a user would. Because automated testing is done through an automation tool, less time is needed in exploratory tests and more time is needed in maintaining test scripts while increasing overall test coverage. Q. 1.1 False sense of quality Not reliable Automation is not testing Demands Maintenance Time and Effort Slow feedback Not many bugs found Q. 2 Inheritance has resulted in some issues involved in testing of object-oriented sof...

Credits to @oliver_photographer Image Link Given the 4  @Test  methods shown, how many times does the  @Before  method execute? The @Before method will execute 4 times because there are 4 @Test's Questions 2, 3, 4, and 5 answers: GitHub Group Repository References: Stackoverflow.com HashcodeVSEquals

Credits to @heftiba Image Link Week 4 Plan: 1. Continue doing research about how to do unit testing or some sort of testing on Android Studio. 2. If research successful do a quick test and make a blog post about it. 3. Finish Chapter 3 Exercises. 4. Each member must do a commit and push to the team's repository on GitHub of the exercises. 5. Get ready for Partial 1 Exam.

Credit to @_louisreed Image Link Week 3 Plan: 1. Research how to do Unit testing in Java. 2. Apply unit testing to some example code. 3. Research how ro do Unit testing on Android Studio. 4. Chapter 3 Exercises 1, 2, 3, 4, 6, and 7 . Week 3 Review: 1. We all researched how to do Unit testing on Java and how to install and get running JUnit on eclipse. It helped a lot that Ken gave us an individual assignment on this and we actually created a blog post on the basic  How To's of JUnit. 2. By working on the exercises that Ken gave us to work on from the book on Chapter 3 we god to test different classes and use JUnit. 3. We had a hard time with this goal of the week because we could find much about it and what we found looked pretty complex so were looking for guidance with our Mobile Apps teacher. 4. We still need to work on exercises 4 and 6. Team #1 Frida  Valentin Floreth

Credits to @bryanminear Image Link JUnit is a testing framework/library for Java (programming language). It is used for both unit testing and UI testing. This helps us define the flow of execution of our code. What is Unit Testing? "Unit testing is the process of examining a small "unit" of software (usually a single class) to verify that it meets its expectations or specification" (Washington Courses, 2019) Setting up JUnit By downloading the newest version of Eclipse, you already have JUnit installed.  If not here's a guide on how to set it up:  Tutorial Creating a JUnit Test Case in Eclipse To use properly JUnit you need to create a separate .java file. In this file is were you are actually going to test your class, so name it something significant for example,  BoundedQueueTest  since in the class im going to test is named  BoundedQueue .   **I'm taking this class from the Introduction to Software Testing book by Paul Amma...