Monthly Archives: December 2016

In memory testing

I really enjoyed this blog because I had never heard of in
memory databases before this. They do however make sense to me. I had always
thought of databases as their own unit, but never really gave much thought to
an in memory one. The fast access for certain programs makes a huge amount of
sense and I can see the uses for them as he gave examples of routing tables and
event poster.
What was interesting is that I can see the use for things
such as router tables, but didn’t give much thought to the testing uses part of
it. Databases can be overwhelmingly large and when it comes to testing, I
imagine that that size comes with a cost, speed. In comes in memory databases
to the rescue. It drastically reduces the time to test because of the speed
that memory works at which in my mind can increase the output of the product
possibly.
I think that if I ever do a lot of testing this is something
that I may indeed try out. You can read more about it here:

http://www.martinfowler.com/bliki/InMemoryTestDatabase.html

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

In memory testing

I really enjoyed this blog because I had never heard of in
memory databases before this. They do however make sense to me. I had always
thought of databases as their own unit, but never really gave much thought to
an in memory one. The fast access for certain programs makes a huge amount of
sense and I can see the uses for them as he gave examples of routing tables and
event poster.
What was interesting is that I can see the use for things
such as router tables, but didn’t give much thought to the testing uses part of
it. Databases can be overwhelmingly large and when it comes to testing, I
imagine that that size comes with a cost, speed. In comes in memory databases
to the rescue. It drastically reduces the time to test because of the speed
that memory works at which in my mind can increase the output of the product
possibly.
I think that if I ever do a lot of testing this is something
that I may indeed try out. You can read more about it here:

http://www.martinfowler.com/bliki/InMemoryTestDatabase.html

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

In memory testing

I really enjoyed this blog because I had never heard of in
memory databases before this. They do however make sense to me. I had always
thought of databases as their own unit, but never really gave much thought to
an in memory one. The fast access for certain programs makes a huge amount of
sense and I can see the uses for them as he gave examples of routing tables and
event poster.
What was interesting is that I can see the use for things
such as router tables, but didn’t give much thought to the testing uses part of
it. Databases can be overwhelmingly large and when it comes to testing, I
imagine that that size comes with a cost, speed. In comes in memory databases
to the rescue. It drastically reduces the time to test because of the speed
that memory works at which in my mind can increase the output of the product
possibly.
I think that if I ever do a lot of testing this is something
that I may indeed try out. You can read more about it here:

http://www.martinfowler.com/bliki/InMemoryTestDatabase.html

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

In memory testing

I really enjoyed this blog because I had never heard of in
memory databases before this. They do however make sense to me. I had always
thought of databases as their own unit, but never really gave much thought to
an in memory one. The fast access for certain programs makes a huge amount of
sense and I can see the uses for them as he gave examples of routing tables and
event poster.
What was interesting is that I can see the use for things
such as router tables, but didn’t give much thought to the testing uses part of
it. Databases can be overwhelmingly large and when it comes to testing, I
imagine that that size comes with a cost, speed. In comes in memory databases
to the rescue. It drastically reduces the time to test because of the speed
that memory works at which in my mind can increase the output of the product
possibly.
I think that if I ever do a lot of testing this is something
that I may indeed try out. You can read more about it here:

http://www.martinfowler.com/bliki/InMemoryTestDatabase.html

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

In memory testing

I really enjoyed this blog because I had never heard of in
memory databases before this. They do however make sense to me. I had always
thought of databases as their own unit, but never really gave much thought to
an in memory one. The fast access for certain programs makes a huge amount of
sense and I can see the uses for them as he gave examples of routing tables and
event poster.
What was interesting is that I can see the use for things
such as router tables, but didn’t give much thought to the testing uses part of
it. Databases can be overwhelmingly large and when it comes to testing, I
imagine that that size comes with a cost, speed. In comes in memory databases
to the rescue. It drastically reduces the time to test because of the speed
that memory works at which in my mind can increase the output of the product
possibly.
I think that if I ever do a lot of testing this is something
that I may indeed try out. You can read more about it here:

http://www.martinfowler.com/bliki/InMemoryTestDatabase.html

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

In memory testing

I really enjoyed this blog because I had never heard of in
memory databases before this. They do however make sense to me. I had always
thought of databases as their own unit, but never really gave much thought to
an in memory one. The fast access for certain programs makes a huge amount of
sense and I can see the uses for them as he gave examples of routing tables and
event poster.
What was interesting is that I can see the use for things
such as router tables, but didn’t give much thought to the testing uses part of
it. Databases can be overwhelmingly large and when it comes to testing, I
imagine that that size comes with a cost, speed. In comes in memory databases
to the rescue. It drastically reduces the time to test because of the speed
that memory works at which in my mind can increase the output of the product
possibly.
I think that if I ever do a lot of testing this is something
that I may indeed try out. You can read more about it here:

http://www.martinfowler.com/bliki/InMemoryTestDatabase.html

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

In memory testing

I really enjoyed this blog because I had never heard of in memory databases before this. They do however make sense to me. I had always thought of databases as their own unit, but never really gave much thought to an in memory one. The fast access for certain programs makes a huge amount of sense and I can see the uses for them as he gave examples of routing tables and event poster.
What was interesting is that I can see the use for things such as router tables, but didn’t give much thought to the testing uses part of it. Databases can be overwhelmingly large and when it comes to testing, I imagine that that size comes with a cost, speed. In comes in memory databases to the rescue. It drastically reduces the time to test because of the speed that memory works at which in my mind can increase the output of the product possibly.
I think that if I ever do a lot of testing this is something that I may indeed try out. You can read more about it here:

http://www.martinfowler.com/bliki/InMemoryTestDatabase.html

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

Hadoop

Installing Hadoop ran into issues initially with the fact that the document for installing is outdated. The mirror link for getting Hadoop is 404ed. The Java version moved onto 8 instead of using 7.  I chose the latest stable version (2.7.3) on the Hadoop website to install.

Instead of using my account, I created a Hadoop account and sshed using that. Ubuntu does not Sudo by default so I had Sudo my Hadoop account or else anything accessing root will be blocked. I also ran into issues where NameNode and DataNode would not start up at all no matter what I did. After experimenting I realized that forcing a creation of hdfs folder with namenode and datanode was conflicting with what Hadoop wanted to do. Hadoop now automatically create both directories which allows my Hadoop to run smoothly.

The experiment I did with Hadoop is the word count example which WordCount.java will compute the word frequency of all text files in the HDFS input directory.  Using the program, I began to understood the advantage of using Hadoop. The MapReduce job splits the data and processes them in multiple parallel processing.  This seems especially advantageous working with multiple larger files.

 

http://hadoop.apache.org/

http://www.michael-noll.com/tutorials/running-hadoop-on-ubuntu-linux-single-node-cluster/

http://www.michael-noll.com/tutorials/running-hadoop-on-ubuntu-linux-single-node-cluster/

From the blog CS@Worcester – Site Title by nealw5 and used with permission of the author. All other rights reserved by the author.

5 Excuses Every Software Tester Must Stop Giving

Week 12 blog post for Software Testing

This week i have decided to read 5 Excuses Every Software Tester Must Stop Giving by Mahesh C..

As i am still relatively new to the world of software testing i am very interested in what exactly software testers do on a daily basis. What better way to do that then by looking at excuses software testers make very frequently, it was my hope to gain insight into the software testing world through this article.

The first excuse was “we don’t control our Test Environment, we have limited access”. The article then goes over the benefits of being able to fully control the environment. an example of this being ” You know all involved components, all software used along with their versions for your product to function. With time, trust me you will have many insights about their working, limitations and possible failure points.”. More importantly it discusses how you can actually do this within a team/ organization. They suggest starting to work very closely with a developer team and start to learn how they do everything and once you have shown competence ask them for control and logically they should give it to you.

The next excuse was “We don’t deploy a build, some other team does it for us”. They then discuss why this is a bad attitude to have, and their explanation is something that resonates with me personally. They suggest that deployment teaches you a lot due to it not always working and failing often means you are forced to learn and debug. This is something that i have personally learned, through my own experience.

Then it goes to “We don’t debug an issue, we find steps and log it”. In order for personal growth it is better to ask yourself a few personal questions and make sure the reason for the bug isn’t easily determined.

4. “I don’t know why it happened. Developer resolved it and i simply verified it”. This is somthing i completely understand. Learn from the developer and thenmaybe next time you won’t need them to fix it and you can do it yourself. A lot of these excuses are just plain lazy from ever perspective.

5. “I didn’t get the opportunity to work on anything else than Manual Testing”. There are time actors involved however there is always that extra bit of time where you could do these things. Again this comes down to the testers being just plain lazy.

From the blog CS@Worcester – Computer Science Journal by jtassone93 and used with permission of the author. All other rights reserved by the author.

The Complete Beginner’s Guide to Responsive Web Design Testing

Week 11 Blog Post for Software Testing

This week i decided to read The Complete Beginner’s Guide to Responsive Web Design Testing by Laxmi

This article was of interest to me because in my Software Construction class i am developing a web application as my final project. Therefore i have become slightly more interested in web design and the testing that is involved with it.

One of the largest issues of this generation is that you do not know if the user will be on a cell phone a tablet a laptop or even a TV and the screen sizes for all of these devices range from 4 inches to 60 inches. Therefore you need to develop your web application in a way that it is able to look good and work properly on all of these devices. they define responsive design as “one website for every screen”. Although it encompasses much more than that. They later go on further to define it as a website designed to have a superior user experience, easy navigation, clear and simple interface, able to adapt easily and work in all resolutions, browsers, screen sizes, hardware, and operating systems.

This is done through flexible layouts, media queries, and flexible media. The issue is how do you test if a website is responsive without pulling it up on all of the possible screen sizes which is impossible to do. This is where software testing tools come in that change the screen size and resolution allowing you to test for a large variety of devices.

As i am developing a web application myself i found this article to be interesting and helpful at the same time. I look forward to optimizing my website using the information that i have learned in order to create a better experience for the user.

From the blog CS@Worcester – Computer Science Journal by jtassone93 and used with permission of the author. All other rights reserved by the author.