Software Quality and Testing

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 @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 @casparrubin Image Link 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 . Work division: Every teammate is Researching the first three points. Floreth: 1, 2 Exercises  Valentin: 3, 4  Exercises Frida: 6, 7  Exercises Team #1 Frida  Valentin Floreth

Credits to @hope_house_press_leather_diary_studio photo-1471970394675-613138e45da3 These were the Goals we set to do on Week 1 : Get familiar and a brief introduction to software testing. Read Chapter 1 of the Introduction to Software Testing Book. Define team roles. Figure out which project are we going to be working on this semester. Share Github credentials (Usernames). Set up Github Team Repository. Brief Review on how to use Github. Get to now each other, by sharing cellphone numbers and creating a WhatsApp group. What we actually  accomplished : We did get acquainted with Software Testing by reading Chapter 1 and solving some doubts with one and other. As for assigning team roles we decided that Frida is going to be our team captain (maybe). We couldn't settle on which project we're going to be working on because we haven't define those projects in our other classes, they're still pretty abstract at the moment. We finish...

Credits to @rawpixel https://unsplash.com/photos/mcLpPD36-2k Get familiar and a brief introduction to software testing. Read Chapter 1 of the Introduction to Software Testing Book. Define team roles. Figure out which project are we going to be working on this semester. Share Github credentials (Usernames). Set up Github Team Repository. Brief Review on how to use Github. Get to now each other, by sharing cellphone numbers and creating a WhatsApp group. Team #1 Frida  Valentin Floreth