Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - hasanmahmud

Pages: 1 ... 4 5 [6]
Scholarship / Master and PhD Scholarship
« on: March 26, 2014, 05:58:44 PM »
Master and PhD Scholarship in Wireless and Emerging Network System (WENS) Laboratory, Kumoh National Institute of Technology, South Korea

From Dept. of IT Convergence, Kumoh National Institute of Technology (KIT), ( is recruiting graduate students (Master and Doctoral student) for Fall Semester 2014 Intake (Start September 2014).

Some research topics in our laboratory are listed below:
•   Next Generation Mobile broadband network (LTE-Advanced, IEEE 802.16m, 5G)
•   Cognitive radio network, software defined radio, and USRP (Universal Software Radio Peripheral)
•   Wireless ad hoc/sensor network
•   Wired/wireless industrial/military network
•   Network/communication protocol and standard
•   Cross-layer optimization
•   Wireless power system
•   Real-time system and real-time OS, Mobile OS and application
•   Low power and power aware embedded system
If anyone wants to join our departments and research activity, we will happily support through our government programs (KGSP) or lab scholarship (WENS Laboratory) which cover tuition fee, living expense and more.

Minimum Requirements:
•   Bachelor / Master Degree in engineering (Electrical, Electronics, Telecommunication, or Computer Engineering/Science)
•   GPA > 3.60 /4.00 (KGSP) or GPA > 3.30/4.00 (lab scholarship)
•   IELTS >5.5, TOEFL IBT> 80, TOEIC > 750 (prerequisite for lab scholarship, optional for KGSP)

If you are interested please send your CV, Academic Transcript, Statement of Purpose and English score, to these email addresses:
Prof. Soo Young Shin:
and also cc :

Tentative Submission Deadline: 31 March 2014

Source : Internet

Applications of Genetic Algorithms in Software Test Automation

The validation of software systems is typically performed by testing them following systematic strategies, thus maximizing chances of uncovering faults. This is particularly important for safety critical systems. It is of the highest practical importance that testing be automated to the fullest extent possible. This implies automatically generating test requirements, test cases, test oracles, and test drivers. In the recent past, researchers and engineers have been exploring the use of various artificial intelligence (AI) techniques so as to address many of these automation issues. A frequent example is the use of genetic algorithms (GAs) to find test inputs that maximize the coverage of source code.
What you will do:
Support researchers on
1.   analyzing the literature on the application of GAs to software testing,
2.   designing and implementing GA algorithms to address specific testing problems,
3.   evaluating the effectiveness of these algorithms on actual case studies, and
4.   implementing these algorithms in user friendly tools.
What you will learn:
You will gain in-depth knowledge of software testing issues and techniques (which are in high demand in industry) and AI search algorithms (such as genetic algorithms), which have widespread applications across many domains.

Source : Internet

Scholarship / Chinese Government Scholarship 2014-2015
« on: March 25, 2014, 04:35:40 PM »
The application of 2014-2015 Chinese Government Scholarship now starts. For the academic year of 2014-2015, altogether 47 seats are available for the Bangladeshi students to apply for.
The Ministry of Education of Bangladesh is responsible for the recommendation of the candidates for the Chinese Government Scholarship. Application must be submitted to the Ministry of Education, the Chinese Embassy in Dhaka will not accept any direct application. As by April 15, the Ministry will make the official recommendation of the candidates to the Chinese Embassy, all the applicants are advised to consult the Ministry to find the deadline for the application.
The Chinese Embassy will hold the interview for the scholarship candidates based on the recommendation by the Ministry of Education of Bangladesh. The interview is tentatively scheduled for April 22-24 in the Confucius Institute at North South University. The time and venue may be subject to change due to the current situation in Bangladesh, all the candidates are advised to pay close attention to the notice on the Chinese Embassy website ( and its Facebook page ( to get the latest information.
Note: The candidates who are absent in the interview will be disqualified.

Application Materials :
Online Information Submission: All the applicants should submit their information on line,  the CSC On-line Application System for Study in China is available at Instructions for on-line application for studying in China under Chinese Government Scholarship is attached hereafter.
Application Materials Submission: The applicants should submit all the following materials to the Scholarship Section of the Ministry of Education of Bangladesh.
1. Application Form for Chinese Government Scholarship ( in Chinese or English). Applicants should start application online and print the application form after submitting it online.
2.  Notarized highest diploma (photocopy). Prospective diploma winners must submit official proof of student status by their current school. Documents in languages other than Chinese or English must be attached with notarized Chinese or English translations.
3. Academic transcripts (notarized photocopy) in Chinese or English.
4. A study plan or research proposal in Chinese or English (A minimum of 200 words for undergraduate, 500 words for non-degree students, and 800 words for postgraduates).
5. Recommendation letters (one original copy and one photocopy): Applicants for graduate program or senior scholar program must submit two letters of recommendation in Chinese or English from professors or associate professors.
6. Applicants for music studies are requested to submit a CD of their own works. Applicants for fine arts programs must submit a CD of their own works which include 2 sketches, 2 color paintings and 2 other works).
7. Applicants under the age of 18 should submit the valid documents of their legal guardians in China.
8. Foreigner Physical Examination Form and Blood Test Report (photocopy). The students must take the original copies of the Form and the Report to China.
9. Applicants with Admission Letter from designated universities should enclose the letter in the application package.
10. Applicants with valid HSK Certificate should enclose it in the application package.

Source :

Science and Information / Software Testing Certification exam List
« on: March 25, 2014, 04:21:24 PM »
Certified Associate in Software Testing: (CAST)
Certified Software Tester: (CSTE)
Certified Manager of Software Testing: (CMST)
ISTQB(International Software Testing Qualifications Board)

Certified Associate in Software Quality: (CASQ)
Certified Software Quality Analyst: (CSQA)
Certified Manager of Software Quality: (CMSQ)

Source : Internet

Software testing
Software testing is an investigation conducted to provide stakeholders with information about the quality of the product or service under test. Software testing can also provide an objective, independent view of the software to allow the business to appreciate and understand the risks of software implementation. Test techniques include, but are not limited to the process of executing a program or application with the intent of finding software bugs .

Defects and failures
Software faults occur through the following processes. A programmer makes an error (mistake), which results in a defect (fault, bug) in the software source code. If this defect is executed, in certain situations the system will produce wrong results, causing a failure. Not all defects will necessarily result in failures. For example, defects in dead code will never result in failures. A defect can turn into a failure when the environment is changed. Examples of these changes in environment include the software being run on a new computer hardware platform, alterations in source data, or interacting with different software. A single defect may result in a wide range of failure symptoms.

Static vs. dynamic testing
There are many approaches to software testing. Reviews, walkthroughs, or inspections are referred to as static testing, whereas actually executing programmed code with a given set of test cases is referred to as dynamic testing. Static testing is often implicit, as proofreading, plus when programming tools/text editors check source code structure or compilers (pre-compilers) check syntax and data flow as static program analysis. Dynamic testing takes place when the program itself is run. Dynamic testing may begin before the program is 100% complete in order to test particular sections of code and are applied to discrete functions or modules. Typical techniques for this are either using stubs/drivers or execution from a debugger environment.

White-Box testing
White-box testing (also known as clear box testing, glass box testing, transparent box testing and structural testing) tests internal structures or workings of a program, as opposed to the functionality exposed to the end-user. In white-box testing an internal perspective of the system, as well as programming skills, are used to design test cases. The tester chooses inputs to exercise paths through the code and determine the appropriate outputs. This is analogous to testing nodes in a circuit, e.g. in-circuit testing (ICT).
While white-box testing can be applied at the unit, integration and system levels of the software testing process, it is usually done at the unit level. It can test paths within a unit, paths between units during integration, and between subsystems during a system–level test. Though this method of test design can uncover many errors or problems, it might not detect unimplemented parts of the specification or missing requirements.

Black-box testing
Black-box testing treats the software as a "black box", examining functionality without any knowledge of internal implementation. The testers are only aware of what the software is supposed to do, not how it does it.[23] Black-box testing methods include: equivalence partitioning, boundary value analysis, all-pairs testing, state transition tables, decision table testing, fuzz testing, model-based testing, use case testing, exploratory testing and specification-based testing.

Grey-box testing
Grey-box testing (American spelling: gray-box testing) involves having knowledge of internal data structures and algorithms for purposes of designing tests, while executing those tests at the user, or black-box level. The tester is not required to have full access to the software's source code. Manipulating input data and formatting output do not qualify as grey-box, because the input and output are clearly outside of the "black box" that we are calling the system under test. This distinction is particularly important when conducting integration testing between two modules of code written by two different developers, where only the interfaces are exposed for test.

Unit testing
Unit testing, also known as component testing, refers to tests that verify the functionality of a specific section of code, usually at the function level. In an object-oriented environment, this is usually at the class level, and the minimal unit tests include the constructors and destructors.[32]
Unit testing is a software development process that involves synchronized application of a broad spectrum of defect prevention and detection strategies in order to reduce software development risks, time, and costs. It is performed by the software developer or engineer during the construction phase of the software development lifecycle. Rather than replace traditional QA focuses, it augments it. Unit testing aims to eliminate construction errors before code is promoted to QA; this strategy is intended to increase the quality of the resulting software as well as the efficiency of the overall development and QA process.

Integration testing
Integration testing is any type of software testing that seeks to verify the interfaces between components against a software design. Software components may be integrated in an iterative way or all together ("big bang"). Normally the former is considered a better practice since it allows interface issues to be located more quickly and fixed.
Integration testing works to expose defects in the interfaces and interaction between integrated components (modules). Progressively larger groups of tested software components corresponding to elements of the architectural design are integrated and tested until the software works as a system.

Component interface testing
The practice of component interface testing can be used to check the handling of data passed between various units, or subsystem components, beyond full integration testing between those units. The data being passed can be considered as "message packets" and the range or data types can be checked, for data generated from one unit, and tested for validity before being passed into another unit. One option for interface testing is to keep a separate log file of data items being passed, often with a timestamp logged to allow analysis of thousands of cases of data passed between units for days or weeks. Tests can include checking the handling of some extreme data values while other interface variables are passed as normal values. Unusual data values in an interface can help explain unexpected performance in the next unit. Component interface testing is a variation of black-box  testing, with the focus on the data values beyond just the related actions of a subsystem component.

System testing
System testing, or end-to-end testing, tests a completely integrated system to verify that it meets its requirements.For example, a system test might involve testing a logon interface, then creating and editing an entry, plus sending or printing results, followed by summary processing or deletion (or archiving) of entries, then logoff.
In addition, the software testing should ensure that the program, as well as working as expected, does not also destroy or partially corrupt its operating environment or cause other processes within that environment to become inoperative (this includes not corrupting shared memory, not consuming or locking up excessive resources and leaving any parallel processes unharmed by its presence

Acceptance testing
At last the system is delivered to the user for Acceptance testing.

Compatibility testing
A common cause of software failure (real or perceived) is a lack of its compatibility with other application software, operating systems (or operating system versions, old or new), or target environments that differ greatly from the original (such as a terminal or GUI application intended to be run on the desktop now being required to become a web application, which must render in a web browser). For example, in the case of a lack of backward compatibility, this can occur because the programmers develop and test software only on the latest version of the target environment, which not all users may be running. This results in the unintended consequence that the latest work may not function on earlier versions of the target environment, or on older hardware that earlier versions of the target environment was capable of using. Sometimes such issues can be fixed by proactively abstracting operating system functionality into a separate program module or library.

Smoke and sanity testing
Sanity testing determines whether it is reasonable to proceed with further testing.
Smoke testing consists of minimal attempts to operate the software, designed to determine whether there are any basic problems that will prevent it from working at all. Such tests can be used as build verification test.

Regression testing
Regression testing focuses on finding defects after a major code change has occurred. Specifically, it seeks to uncover software regressions, as degraded or lost features, including old bugs that have come back. Such regressions occur whenever software functionality that was previously working, correctly, stops working as intended. Typically, regressions occur as an unintended consequence of program changes, when the newly developed part of the software collides with the previously existing code. Common methods of regression testing include re-running previous sets of test-cases and checking whether previously fixed faults have re-emerged. The depth of testing depends on the phase in the release process and the risk of the added features. They can either be complete, for changes added late in the release or deemed to be risky, or be very shallow, consisting of positive tests on each feature, if the changes are early in the release or deemed to be of low risk. Regression testing is typically the largest test effort in commercial software development, due to checking numerous details in prior software features, and even new software can be developed while using some old test-cases to test parts of the new design to ensure prior functionality is still supported.

Acceptance testing
Acceptance testing can mean one of two things:
1.   A smoke test is used as an acceptance test prior to introducing a new build to the main testing process, i.e. before integration or regression.
2.   Acceptance testing performed by the customer, often in their lab environment on their own hardware, is known as user acceptance testing (UAT). Acceptance testing may be performed as part of the hand-off process between any two phases of development

Alpha testing
Alpha testing is simulated or actual operational testing by potential users/customers or an independent test team at the developers' site. Alpha testing is often employed for off-the-shelf software as a form of internal acceptance testing, before the software goes to beta testing.

Beta testing
Beta testing comes after alpha testing and can be considered a form of external user acceptance testing. Versions of the software, known as beta versions, are released to a limited audience outside of the programming team. The software is released to groups of people so that further testing can ensure the product has few faults or bugs. Sometimes, beta versions are made available to the open public to increase the feedback field to a maximal number of future users

Functional vs non-functional testing
Functional testing refers to activities that verify a specific action or function of the code. These are usually found in the code requirements documentation, although some development methodologies work from use cases or user stories. Functional tests tend to answer the question of "can the user do this" or "does this particular feature work."
Non-functional testing refers to aspects of the software that may not be related to a specific function or user action, such as scalability or other performance, behavior under certain constraints, or security. Testing will determine the breaking point, the point at which extremes of scalability or performance leads to unstable execution. Non-functional requirements tend to be

those that reflect the quality of the product, particularly in the context of the suitability perspective of its users.
Software performance testing
Performance testing is generally executed to determine how a system or sub-system performs in terms of responsiveness and stability under a particular workload. It can also serve to investigate, measure, validate or verify other quality attributes of the system, such as scalability, reliability and resource usage.
Load testing is primarily concerned with testing that the system can continue to operate under a specific load, whether that be large quantities of data or a large number of users. This is generally referred to as software scalability. The related load testing activity of when performed as a non-functional activity is often referred to as endurance testing. Volume testing is a way to test software functions even when certain components (for example a file or database) increase radically in size. Stress testing is a way to test reliability under unexpected or rare workloads. Stability testing (often referred to as load or endurance testing) checks to see if the software can continuously function well in or above an acceptable period.
There is little agreement on what the specific goals of performance testing are. The terms load testing, performance testing, scalability testing, and volume testing, are often used interchangeably.

Usability testing
Usability testing is needed to check if the user interface is easy to use and understand. It is concerned mainly with the use of the application.

Security testing
Security testing is essential for software that processes confidential data to prevent system intrusion by hackers

1) Open Source Tools
a) Test Management tools
•   TET (Test Environment Toolkit)
o   The goal behind creating the Test Environment Toolkit (TET) was to produce a test driver that accommodated the then current and anticipated future testing needs of the test development community. To achieve this goal, input from a wide sample of the community was used for the specification and development of TET’s functionality and interfaces.
•   TETware
o   The TETware is the Test Execution Management Systems which allows you to do the test administration, sequencing of test, reporting of the test result in the standard format (IEEE Std 1003.3 1991) and this tools is supports both UNIX as well as 32-bit Microsoft Windows operating systems, so portability of this is with test cases you developed. The TETware tools allow testers to work on a single, standard, test harness, which helps you to deliver software projects on time. This is easily available for download on ftp download.
•   Test Manager
o   The Test Manager is an automated software testing tool is used in day to days testing activities. The Java programming language is used to develop this tool. Such Test Management tools are used to facilitate regular Software Development activities, automate & mange the testing activities. Currently Test Manager 2.1.0 is ready for download. If you want to learn more information of Test Manager, Click here to get a latest copy for free.
•   RTH
o   RTH is called as “Requirements and Testing Hub”. This is a open source test management tool where you can use as requirement management tool along with this it also provides the bug tracking facilities. From here you can download the latest version of RTH.
b) Functional Testing Tools
•   Selenium
•   Soapui
•   Watir
•   HTTP::Recorder
•   WatiN
•   Canoo WebTest
•   Webcorder
•   Solex
•   Imprimatur
•   Swete
•   ITP
•   WET
•   WebInject
c) Load Testing Tools
•   Jmeter
•   FunkLoad
2) Proprietary/Commercial tools
a) Test Management tools
•   HP Quality Center/ALM
•   QA Complete
•   T-Plan Professional
•   Automated Test Designer (ATD)
•   Testuff
•   QAS.TCS (Test Case Studio)
•   PractiTest
•   Test Manager Adaptors
•   SpiraTest
•   TestLog
•   ApTest Manager
•   DevTest
b) Functional Testing Tools
•   QuickTest Pro
•   Rational Robot
•   Sahi
•   SoapTest
•   Badboy
•   Test Complete
•   QA Wizard
•   Netvantage Functional Tester
•   PesterCat
•   AppsWatch
•   Squish
•   actiWATE
•   liSA
•   vTest
•   Internet Macros
•   Ranorex
c) Load Testing Tools
•   HP LoadRunner
•   LoadStorm
•   NeoLoad
•   Loadtracer
•   WebLOAD Professional
•   Forecast
•   ANTS – Advanced .NET Testing System
•   vPerformer
•   Webserver Stress Tool
•   preVue-ASCII
•   Load Impact

Pages: 1 ... 4 5 [6]