Skip to main content

Can I use constructors with in Unit Test?

Actually the answer is yes but not recommended. This problem came to my mind time ago at the start of selenium project. I used and end-up with many run time errors. If you use constructors then your test project will build without error but there can be run time error specially when calling it by other class.


First as a QA what we need to understand is why we are using unit test. Unit testing is testing the public states, behaviors, and interactions of testing objects. If you use private fields within constructors then what there to be test. In fact we need to use object orient concepts but better to keep the focus on simplicity.

Comments

Popular posts from this blog

Accessibility Testing

Accessibility Testing is a non-functional testing type. This means anyone can use a particular web application, mobile application, website, or any other software package. Any human means not only perfect men or women but also differently able people as well. Things can be used for testing, 

Differences between Severity ,Priority and Status

In market there are many bug tracking and project management tools available. These tools allow us to keep essential information of a bug or task. You will see there are three places have to fill when key in a task. Those three places are Status, Priority and Status of a bug/task. Let's see what those stand for.  Severity Priority Status Connotation Severity of a bug means how much it affecting to functionality of the software. Total damage it can do. Priority means how fast a bug or task should be resolve. Status means the current position of the bug/task. Types            Critical            Major            Moderate            Minor           Cosmetic           Low           Medium           High           New           Active/Open           Resolved/Fixed           QA In progress           Reopen           Closed/Completed 

MVC Architecture

Model-View-Controller (MVC) is a design pattern recently most popular among software engineers for applications which are needed to provide multiple views with using same data. I am suggesting MVC is better than WCF, because of this module separation. For an examples       ·          Multiple views and controllers can interface with same model for modification even those never exist before add this model.       ·          It is supporting all type of HTML verbs.       ·          No view state and post back events.       ·          Easy integration with JavaScript framework.       ·          Helps to decrease complexity of project       ·          Provides RAD development ( http://en.wikipedia.org/wiki/Rapid_application_development ).