Planning Week 4

At the start of the semester we planned that during this week we will be setting everything up to test the project continuously in the development. The project will now be only a web application, so we need to install all the essential tools to test JavaScript code, front-end functionality and data base communication.

At the end of this week we should have everything ready in the repository and some demo tests working. This includes the Travis set-up that will allow us control pull requests automatically.

Anuncio publicitario

Planning week 3

This week we are going to do a little bit more of research on the selected frameworks and tools we decide, as we stated on the semester plan. For this project we decided that we are going to use mostly Java for Android, SOLID for the database and Go for the back-end. Each one of us is going to learn through tutorials and guides a specific tool for testing and at the end of the week we are going to write down the conclusions in another post. For this week the assignments are:

Carlos Alberto Rueda: Do research of a Go testing tool, pick one and learn to use it.

Jesus Alberto Alvarez: Learn to use Espresso for testing Android UI.

José Carlos Peñuelas: Learn to use JUnit for automated Java tests.

Adler Zamora: Learn to install and use NightmareJS for several front-end tests.

It’s important to say that this doesn’t mean that this is not what each one if use is going to work on the whole semester. We just want to learn a little bit about setting up the tools and add them to our project from the beginning in case that we need them. Some things might(will) change or some tools are not going to be needed. Also, we should be able to explain how to explain the usage of a testing tool to our partners so that they can write tests too. The point of this is that whenever we need more work on one part of the project we could help others to test on any framework we use.

Semester plan

This semester is going to last 14 weeks, and for watch one we have activities to be done and requirements to fulfill to make our project. We are going to be doing the testing part of an already existing project of another class from one of my partners. The product is probably a web application o our planning must try to cover everything from building the environment and testing the final product. Of course, this plan is probably going to fail as we don’t know very much about the requirements or tools we are going to use. However, it’s always good to have some idea of what we should be doing in each week. The plan for each week is the next one:

Week 1: Research for development and testing tools.
Week 2: Decide for the tools we are going to use and learn to use them.
Week 3: Develop the base of the project and have functional automated tests.
Week 4 and 6: Back-end configurations and testing connectivity.
Week 7 and 9: Initial tests for general features and work on them.
Week 10 and 11: Continue on the development of features.
Week 12 and 14: Requirements verification and validate the final product.

During this week we want to do some research for the tools that are available for coding and testing with more efficiency. We are going to write a document that has all our research by Saturday, this will help us to take a decision for the next week and start learning how to use the tools we choose. Our goal for this class with this project is to learn to implement the best practices for testing, we are going to try to have automated unit testing and integration testing.