Skip to main content

Posts

Showing posts from May, 2017

NoSQL Databases

EclEmma for code coverage

What is code coverage?                  Code coverage analysis is a structural testing technique (AKA glass box testing and white box testing). Structural testing is also called path testing since you choose test cases that cause paths to be taken through the structure of the program.  Code coverage is a measure used to describe the degree to which the source code  of a program  is executed when a particular test suits  runs. A program with high code coverage, measured as a percentage, has had more of its source code executed during testing which suggests it has a lower chance of containing undetected software bugs  compared to a program with low code coverage. What is EclEmma? This is a plugin for Eclipse which will shows you the coverage of a specific test set. You can run these on you Junit tests to check which statements are executed and which are not. there will be three main colors after you run this...

Online Bug Tracking System

TRELLO While I was doing my SLIIT SA Assignment I found a cool online application for Bug Tracking. This keeps track of the Bugs which were identified, you can assign the task to a developer, whether it was solved, by whom etc. It even enables you to attach documents, labels, comment and these things are getting updated instantly. Its a User Friendly application which is totally free. The link is - https://trello.com/ Also if you want a guide please check the below link - https://www.youtube.com/watch?v=xky48zyL9iA  

Overview of the Second Year ITP project

While I was doing this project I learnt a lot which are related to the coding and also how to work as a team. I was the team leader and I had to communicate / guide seven members while I was working. From the initial  report until the final report I had to draft them. I had to draw the ER diagram, Class Diagram, Use Case Diagrams,  Use Case Scenarios, State Chart Diagrams, Class Diagrams. Actually even finishing this project was a real stress at the end we were manged to finish it with a good output with the help of some team members.