Software Quality and Testing

Exam 1 Software quality and testing 1. Define each of: Software fault: static error in the code. Software error: internal, not a normal behavior of the program due to a fault. Software failure: external, visible failure of the program. That it doesn't work basically. 2. List 5 levels of test process maturity.  Level 0: Testing and debugging are the same. (Worst level) Level 1: Testing is only to find that your code doesn't work. Level 2: Get defensive or make an issue personal with testers because they broke your code. Level 3: Understand the job of a tester and take feedback as constructive criticism. Level 4: Become an expert software tester and make extreme good quality software. Work in harmony with testers. 3. Explain difference between revenue tasks and excise tasks. Revenue tasks contribute directly to the solution of a problem, and excise tasks do not. Excise tasks are candidates for automation, revenue tasks are not. 4. Authors, History...

Credits to @chesteralvarez Image Link What is DevOps? Is the blending of the roles of developers and operations support.  Example: In application service, developers write the code that is deployed* into application service. Operations team maintains the application server. If the application fails to work on deployment there is a knowledge gap. People with knowledge of both software development and operations are required to bridge this gap, this is where DevOps practitioners are required. deployed*: Software deployment includes all the process required for preparing a software application to run and operate in a specific environment. It involves installation, configuration, testing and making changes to optimize the performance of the software. It can either be carried out manually or through automated systems. How it is important to the software engineering process? The software development lifecycle is complex and has a number of important phases which include:...

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...