How can SQL help your testing abilities? (Week 5)

The reports that SQL can generate transforms raw information into useful data also can be used as a tool that can help to refine your testing abilities. The methods that SQL provide can help perfect the skills of programmers. The methods help to get correct results  when we testing back-end applications.SQL is a parent-child relationship schema that allows information to be accessible and allows to minimize discrepancies across data which create reliable output tables.The tables with columns and rows that build up the records of employment can help the End user have a interactive graphical Interface. The interactive graphical interface it can help the users to make changes. SQL is used in a variety of testing tools; the tools that are used
mostly to select information that is relevant and can provide insight
into the business practices. Some of the automation tools that is used
to create a quality product are QTP and Selenium. QTP
provides functional test automation for software applications and environments and Selenium is a free (open source) automated testing suite, Selenium is used to test web applications. Both tools use different languages QTP  run on Java and Selenium runs on VBscript. There are some global statements that are used from SQL one of the statements is the sorted procedure. The advantage of Sorted procedure is that it can minimize work and it can decrise the amount of time it requires for testing by preventing reniventing the wheel. SQL have more capabilities available, which makes it helpful tool when we have to verify data.If we use these methods we can get better testing results.
Citation
https://www.utest.com/articles/how-can-sql-help-your-testing-abilities

From the blog Table of Code by Andon S and used with permission of the author. All other rights reserved by the author.

How can SQL help your testing abilities? (Week 5)

The reports that SQL can generate transforms raw information into useful data also can be used as a tool that can help to refine your testing abilities. The methods that SQL provide can help perfect the skills of programmers. The methods help to get correct results  when we testing back-end applications.SQL is a parent-child relationship schema that allows information to be accessible and allows to minimize discrepancies across data which create reliable output tables.The tables with columns and rows that build up the records of employment can help the End user have a interactive graphical Interface. The interactive graphical interface it can help the users to make changes. SQL is used in a variety of testing tools; the tools that are used
mostly to select information that is relevant and can provide insight
into the business practices. Some of the automation tools that is used
to create a quality product are QTP and Selenium. QTP
provides functional test automation for software applications and environments and Selenium is a free (open source) automated testing suite, Selenium is used to test web applications. Both tools use different languages QTP  run on Java and Selenium runs on VBscript. There are some global statements that are used from SQL one of the statements is the sorted procedure. The advantage of Sorted procedure is that it can minimize work and it can decrise the amount of time it requires for testing by preventing reniventing the wheel. SQL have more capabilities available, which makes it helpful tool when we have to verify data.If we use these methods we can get better testing results.
Citation
https://www.utest.com/articles/how-can-sql-help-your-testing-abilities

From the blog Table of Code by Andon S and used with permission of the author. All other rights reserved by the author.

How can SQL help your testing abilities? (Week 5)

The reports that SQL can generate transforms raw information into useful data also can be used as a tool that can help to refine your testing abilities. The methods that SQL provide can help perfect the skills of programmers. The methods help to get correct results  when we testing back-end applications.SQL is a parent-child relationship schema that allows information to be accessible and allows to minimize discrepancies across data which create reliable output tables.The tables with columns and rows that build up the records of employment can help the End user have a interactive graphical Interface. The interactive graphical interface it can help the users to make changes. SQL is used in a variety of testing tools; the tools that are used
mostly to select information that is relevant and can provide insight
into the business practices. Some of the automation tools that is used
to create a quality product are QTP and Selenium. QTP
provides functional test automation for software applications and environments and Selenium is a free (open source) automated testing suite, Selenium is used to test web applications. Both tools use different languages QTP  run on Java and Selenium runs on VBscript. There are some global statements that are used from SQL one of the statements is the sorted procedure. The advantage of Sorted procedure is that it can minimize work and it can decrise the amount of time it requires for testing by preventing reniventing the wheel. SQL have more capabilities available, which makes it helpful tool when we have to verify data.If we use these methods we can get better testing results.
Citation
https://www.utest.com/articles/how-can-sql-help-your-testing-abilities

From the blog Table of Code by Andon S and used with permission of the author. All other rights reserved by the author.

How can SQL help your testing abilities? (Week 5)

The reports that SQL can generate transforms raw information into useful data also can be used as a tool that can help to refine your testing abilities. The methods that SQL provide can help perfect the skills of programmers. The methods help to get correct results  when we testing back-end applications.SQL is a parent-child relationship schema that allows information to be accessible and allows to minimize discrepancies across data which create reliable output tables.The tables with columns and rows that build up the records of employment can help the End user have a interactive graphical Interface. The interactive graphical interface it can help the users to make changes. SQL is used in a variety of testing tools; the tools that are used
mostly to select information that is relevant and can provide insight
into the business practices. Some of the automation tools that is used
to create a quality product are QTP and Selenium. QTP
provides functional test automation for software applications and environments and Selenium is a free (open source) automated testing suite, Selenium is used to test web applications. Both tools use different languages QTP  run on Java and Selenium runs on VBscript. There are some global statements that are used from SQL one of the statements is the sorted procedure. The advantage of Sorted procedure is that it can minimize work and it can decrise the amount of time it requires for testing by preventing reniventing the wheel. SQL have more capabilities available, which makes it helpful tool when we have to verify data.If we use these methods we can get better testing results.
Citation
https://www.utest.com/articles/how-can-sql-help-your-testing-abilities

From the blog Table of Code by Andon S and used with permission of the author. All other rights reserved by the author.

How To Be The Terminator (10/21/16 Week 5)

It is your duty to protect the world from devastation.. the world of the software you are working on that is!

Fret not, it is not a difficult task. Previously, it has been mentioned the tactics of organization has led to perfect control and containment of peace amongst the living entity known as the source code.  However, it is not until one is in the moment where they realize it was easier said than done. They may have had a basic plan to tackle infestation of software bugs letting the tranquility of software compile happily, but one can not be too prepared when about to face what they are looking for. One must know how to REACT.

You are not just a software tester. You are a pokemon trainer, Indiana Jones, and Sherlock Holmes. You are just about everything that you need to be before you become the terminator itself!

9100616-cartoon-superhero-office-nerd-punching-the-air-stock-vector

You may have spotted a bug, but it wasn’t a satisfying as the bug when away forcing you to reproduce what ever you did to bring it back. This is where you put your pokemon hat on and grab those pokeballs, as you go retracing your steps finding the creature you wanted to catch before.

Once you have captured your bug, its not over. There could be more bugs located around the area where the bug you found and reported was. You must scan the surrounding of the code itself and use your discoveries to find the treasure (the other bugs). It doesn’t hurt to pretend wearing a cowboy hat while you do that too.

After scoping out the area, the magnifying glass will help you analyze the data other findings you may have encountered in which you can estimate a rough idea of how far certain problems can spread or how severe they can be when the software is launched.

Lastly, all information must be reported to the headquarters. Once everyone is aware, the process of termination can begin. After shining the spotlight on the possible trouble that may negatively effect the sweet result of the creation, the evil pesticides may be overridden and the world may be saved once again.

Just remember to REACT properly, and as a QA tester you should feel proud of yourself. Your actions have you been deemed as a super hero… cape may or may not be included. Your identity may be anonymous to the public, but rest assured no good deed goes unpunished. As long as you stay by the morals of Reproducing, Exploring, Analyzing, Communicating, and Triage, you may be one step closer on ending the epidemic of a bug-riddling source code.

(source: http://www.brendanconnolly.net/react-to-bugs/)

From the blog CS@Worcester – Dan's Tech Rant by danbarbara and used with permission of the author. All other rights reserved by the author.

Maven

This week I read the first chapter of a book called Introducing Maven(by Balaji Varanasi). Maven makes software development much easier; there are 2 main benefits that Maven provides.

  1. Standardized directory structure
  2. Declarative dependency management

For me the most useful feature of Maven is its standardized directory structure for projects. It is much easier for me to navigate through different projects if they all share the same structure.

Dependency management is feature that automate dependency management. Instead of manually downloading dependencies and keeping track of their versions, we could use Maven to do it for us. Information regarding the project dependencies is stored in the pom.xml file. The pom.xml file stores the what not the how. Maven then automatically downloads the dependencies and allows us to use it in the project.

 

 

 

 

From the blog Software Testing – The blog about software by Sudarshan and used with permission of the author. All other rights reserved by the author.

Week 1 – A Mnemonic Worth REACTing To

the_reaction_by_tee_kyrin-d4h4jzr

  • Reproduce
  • Explore
  • Analyze
  • Communicate
  • Triage

Every tester has to deal with bugs, but how should we deal with them? Brendan Connolly suggests that we REACT.  Connolly says that the first step in resolving a bug is to REPRODUCE the bug by tracking down the steps that caused it.  The next Step is to EXPLORE the nature of the bug.  Connolly warns that acting too hastily can create more problems than the bug does.  The next step is to ANALYZE the severity of the bug.  Steps one and two have given you an idea of how big the bug is and where it is, step three is where you must decide which action you should take based on the impact of the bug.  Now it is time to COMMUNICATE.  The next step is to report the bug, either to a bug tracking system, your team, etc.  Finally, the last step is TRIAGE.  After the bug is reported, the process isn’t over.  You must continue to clarify the issue as best you can.

From the blog cs443 – TayNock's Blog by taynock and used with permission of the author. All other rights reserved by the author.

Read this and you’ll Know more about Design Patterns than you ever did!

Context: Engineers look for routine solutions before resorting to original problem solving. Design is probably the most challenging activity in the software development life cycle. There is no algorithm for deriving abstract solution models from requirements. The best the discipline of software engineering can offer are methods, techniques, heuristics, and design patterns.

Solution: A design pattern is problem-solution pair. Design patterns are discovered rather than invented. Design patterns are paragons of good design. A design pattern, and more generally a design, is an abstraction of an implementation. What is being reused is the structure or organization of the code. The solution provided is the design and not the code. A design pattern is not a concrete design or implementation, such as an algorithm that can be used as-is, but rather a generic solution that must be adapted to the specific needs of the problem at hand. The purpose of the design process is to determine how the eventual code will be structured or organized into modules. The output of the design process is an abstract solution model typically expressed with a symbolic modeling language such as UML.

Pros:

  • Studying design patterns helps to develop the intellectual concepts and principles needed to solve unique design problems from first principles. Design patterns define a shared vocabulary for discussing design and architecture. Catalogs of design patterns define a shared vocabulary at the right level of abstraction for efficient communication of design ideas.
  • Knowing popular design patterns make it easier to learn class libraries that use design patterns. For example, the classes and interfaces that make up the Java IO package are confusing to many new Java programmers simply because they aren’t familiar with the decorator design pattern.
  • Knowledge of design patterns simplifies software design by reducing the number of design problems that must be solved from first principles. Design problems that match documented design patterns have ready-made solutions. The remaining problems that don’t match documented design patterns must be solved from first principles.

Cons (not really! lol):

  • Applying design patterns is easier than solving design problems from first principles but their application still requires thoughtful decision making. You must be familiar enough with existing patterns to recognize the problem is one for which a design pattern exists.

Here’s the important things to remember:

  • First, design (and more generally engineering) is about balancing conflicting forces or constraints.
  • Second, design patterns provide general solutions at a medium level of abstraction. They don’t give exact answers, and at the same time, they are more concrete and practical than abstract principles or strategies.
  • Finally, patterns aren’t dogma.

Here’s where Kids get Confused:

Intent Matters!!!!!

Design patterns are NOT distinguished by their static structure alone.

Can you tell me which represents state pattern and which represents strategy pattern?

1

It is of course impossible. What makes a design pattern unique is its intent? The intent of a pattern is the problem solved or reason for using it. The intent of State pattern is to allow an object to alter its behavior when its internal state changes. The intent of the Strategy pattern is to encapsulate different algorithms or behaviors and make them interchangeable from the client’s perspective. The structure is the same for both solutions.

Works Cited:

Burris, Eddie. “Introduction to Design Patterns.” Programming in the Large with Design Patterns. Leawood, Kan: Pretty Print, 2012. 11-33. Print.

From the blog CS@Worcester – thewisedevloper by thewisedeveloper and used with permission of the author. All other rights reserved by the author.

Google Testing Blog: Hackable Projects – Pillar 2: Debuggability

Hackable Projects – Pillar 2: Debuggability

This is a continuation of Patrik Höglund series about how to make your software hackable. (If you have not read the first article, here is the link: first article)

Patrik Höglund continues to talk about how to make your code more hackable by going on to his second pillar of hackability: Debuggability. However here this word doesn’t simple mean running a debugger on your code and calling it a day. Höglund explains debuggability as “being able to easily find what’s wrong with a piece of software, whether it’s through logs, statistics or debugger tools.” To help with this process, Höglund goes over a few examples that help their developers with debuggability.
The first one is running your project on a local host. This way you not only get around the possibility of crashing your main servers, but you can also set up “scripts that invoke the server binaries with flags.” This helps to make debugging and developing your server a simpler process overall. Höglund then goes into how to debug for mobile apps. He suggests using unit tests here as well since they have great hackability. He then gives some suggestions for software to use for debugging on iOS and Andriod. Höglund then some tips for when debugging gets tricky.
The next step that Höglund brings up is making sure that you have proper logging.He links another article to look at, but he states that you should make sure that you are getting proper stack traces instead of going off of an error message. He also says that there is such a thing as too much logging which can lead to having your project be less hackable. The other thing Höglund brings up to make sure that you can use statistics to your advantage. If you run a monitoring system, like Stackdriver for Google Cloud, Höglund says that “tools can help you keep track of request volumes and error rates.” This lets you find errors quicker and allows you to rollback bad code as soons as possible.
The last thing that Höglund talks about is System Under Test (SUT) Size. He says that “small and focused tests aid debuggability, because when a test breaks there isn’t an enormous SUT to look for errors in,” and makes tests more reliable. He refers to this article for information about SUT.

From the blog CS WSU – Techni-Cat by clamberthutchinson and used with permission of the author. All other rights reserved by the author.

A bit off topic on Agile

I think this week I would like to go off topic and talk about Agile development or Extreme programming. I believe we were able to stray off for one blog if I recall correctly. Up until now I haven’t really given much thought to actual processes for design patterns and how an actual project is created using Extreme programming and test driven development. I am finding that I may have to take a step back rethink what I have thought to be the way things were done. As I have zero experience in an actual programming position in a company and only know what I read or learn here at school, I find that I am having to rethink things out often. Anyways my thoughts on TDD and XP. I am finding some of the concepts hard to grasp, not intellectually, but just in a common sense strategy sort of way. We just finished a lab on TDD and XP and the method of programming to me seems counterintuitive in ways, but I think it is just because it is new. I do like the idea of writing a test and then the method and just doing the basics to get it to work and building from there. I have never given this much thought, but hey if you write the test you know what to code for so it’s pretty cool. I also will have to get use to the idea of not using inheritance when possible and using many smaller methods to make up the project as whole. I don’t think I will have too much of a hard time adjusting to that though as I think that this is a very effective way to do things as it is easier to compartmentalize when there is an issue with the code and to track bugs down I would imagine as each small part is part of a whole so you only have to weed out a small potion and make changes instead combing over mass quantities of code. Over all I think that once I get use to this way of thought it will only help to make me a better programmer.

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