Thursday, September 8, 2011
VIDEO : Search Engine Marketing
The 5 Rs of Search Engine Marketing with Bryan Eisenberg
Read more about SEM - Search Engine Marketing
Read more about SEM - Search Engine Marketing
Wednesday, September 7, 2011
Thursday, September 1, 2011
VIDEO : Software Testing
Understanding Requirements, Scenarios, Test Cases, Test Sets and Test Scripts with Rommana
Learn more about Software Testing
Learn more about Software Testing
What is Software Testing?
Author Bio :
Samuel worked for TestLogistics, TestLogistics is a leading provider of Testing Logistics Solutions (including Performance Testing Test Environments Management, Test Data Management, Harnessing and Test Lab Operations), Technical Testing Solutions (i.e. Performance Testing, Infrastructure, Security, SOA & Test Automation) & Senior Test Consulting Strategy. TestLogistics provide top tier organisations with a range of services which enable significant improvements on quality, delivery and overall value.
Quickly I’d say: Software Testing is the function of trying to find defects throughout the software lifecycle.
However to add more context. I always like to responds with the three P’s – Process, Products & People
Process
From an process (or activity) perspective, one might describe the software lifecycle succinctly as:
1. Test Strategy
2. Planning
3. Test Analysis
4. Test Case Design
5. Construction and Verification
6. Testing Execution Cycles
7. Post Implementation Testing or Reviews
Product
From a product (or artefact) perspective, one my describe the software lifecycle as consisting of the following deliverables:
(A) Test Strategy
(B) Test Plan(s)
(C) Test Cases
(D) Test Results
(E) Defect Logs
(F) Status Reports
People
And from a people (or Organisational) perspective I’d say
(A) Test Manager – To run Strategy, Planning & Executive Reporting
(B) Test Leads – To run team coordination, test suite coverage & reporting
(C) Test Analysts – To develop test cases, do execution and defect tracking
Want to know more about the basics of software testing?
Then contact TestLogistics (www.TestLogistics.Net) and have a look at some of their blueprints that describe each of the areas and more in detail.
Samuel worked for TestLogistics, TestLogistics is a leading provider of Testing Logistics Solutions (including Performance Testing Test Environments Management, Test Data Management, Harnessing and Test Lab Operations), Technical Testing Solutions (i.e. Performance Testing, Infrastructure, Security, SOA & Test Automation) & Senior Test Consulting Strategy. TestLogistics provide top tier organisations with a range of services which enable significant improvements on quality, delivery and overall value.
Quickly I’d say: Software Testing is the function of trying to find defects throughout the software lifecycle.
However to add more context. I always like to responds with the three P’s – Process, Products & People
Process
From an process (or activity) perspective, one might describe the software lifecycle succinctly as:
1. Test Strategy
2. Planning
3. Test Analysis
4. Test Case Design
5. Construction and Verification
6. Testing Execution Cycles
7. Post Implementation Testing or Reviews
Product
From a product (or artefact) perspective, one my describe the software lifecycle as consisting of the following deliverables:
(A) Test Strategy
(B) Test Plan(s)
(C) Test Cases
(D) Test Results
(E) Defect Logs
(F) Status Reports
People
And from a people (or Organisational) perspective I’d say
(A) Test Manager – To run Strategy, Planning & Executive Reporting
(B) Test Leads – To run team coordination, test suite coverage & reporting
(C) Test Analysts – To develop test cases, do execution and defect tracking
Want to know more about the basics of software testing?
Then contact TestLogistics (www.TestLogistics.Net) and have a look at some of their blueprints that describe each of the areas and more in detail.
What is Test Environments Management?
Author Bio :
Samuel worked for TestLogistics, TestLogistics is a leading provider of Testing Logistics Solutions (including Test Environments Management, Test Data Management, Harnessing and Test Lab Operations), Technical Testing Solutions (i.e. Performance Testing, Infrastructure, Security, SOA & Test Automation) & Senior Test Consulting Strategy. TestLogistics provide top tier organisations with a range of services which enable significant improvements on quality, delivery and overall value.
A significant proportion of “Test Related” costs* are associated with Test Environment and Data problems. These problems range from:
Poor Test Environment Requirements,
Test Environment Un-Readiness,
Test Environment Misconfiguration,
Test Environment Unsuitability,
Test Environment Inflexibility,
Test Environment Outages and
Test Environment Resource Contention
Note: Recent surveys by the TestLogistics Company (www.testlogistics.net) have identified that most companies claimed that 20%-40% of total testing cost could be attributed to immature Test Environments and Test Data activity and/or issues.
In an attempt to address these issues, a focused and timely Test Environment Management (TEM) ability is necessary. That is, an ability that promotes the understanding of one's Environments and applies that knowledge, with appropriate mix of governance, technology and resource to provision and share environments based on business & project needs.
Niall Crawford (CIO) of TestLogistics (and previously a Test Environments & Configuration Management Practitioner) believes 8 key areas must be addressed as you evolve your TEM maturity, these are:
Environment Knowledge Management
Consistent Test Environment Requirements Definition
Environment Booking Process
Assessment & Approval Mechanisms
Planning & Release Procedures
Environments Invocation (Lab & Datacenter Orchestration)
Environments Service Management
Environments Termination
Further “deep dive” information of each of these areas can be provided through the “Test Environments Blueprint” ©TestLogistics, a blueprint designed by to help people visualize the key areas of focus when developing a model to address the Test Environment Needs of a major enterprise.
Samuel worked for TestLogistics, TestLogistics is a leading provider of Testing Logistics Solutions (including Test Environments Management, Test Data Management, Harnessing and Test Lab Operations), Technical Testing Solutions (i.e. Performance Testing, Infrastructure, Security, SOA & Test Automation) & Senior Test Consulting Strategy. TestLogistics provide top tier organisations with a range of services which enable significant improvements on quality, delivery and overall value.
A significant proportion of “Test Related” costs* are associated with Test Environment and Data problems. These problems range from:
Poor Test Environment Requirements,
Test Environment Un-Readiness,
Test Environment Misconfiguration,
Test Environment Unsuitability,
Test Environment Inflexibility,
Test Environment Outages and
Test Environment Resource Contention
Note: Recent surveys by the TestLogistics Company (www.testlogistics.net) have identified that most companies claimed that 20%-40% of total testing cost could be attributed to immature Test Environments and Test Data activity and/or issues.
In an attempt to address these issues, a focused and timely Test Environment Management (TEM) ability is necessary. That is, an ability that promotes the understanding of one's Environments and applies that knowledge, with appropriate mix of governance, technology and resource to provision and share environments based on business & project needs.
Niall Crawford (CIO) of TestLogistics (and previously a Test Environments & Configuration Management Practitioner) believes 8 key areas must be addressed as you evolve your TEM maturity, these are:
Environment Knowledge Management
Consistent Test Environment Requirements Definition
Environment Booking Process
Assessment & Approval Mechanisms
Planning & Release Procedures
Environments Invocation (Lab & Datacenter Orchestration)
Environments Service Management
Environments Termination
Further “deep dive” information of each of these areas can be provided through the “Test Environments Blueprint” ©TestLogistics, a blueprint designed by to help people visualize the key areas of focus when developing a model to address the Test Environment Needs of a major enterprise.
Practical Security Infrastructure Testing
Author Bio :
Samuel worked for TestLogistics, TestLogistics is a leading provider of Testing Logistics Solutions (including Test Environments Management, Test Data Management, Harnessing and Test Lab Operations), Technical Testing Solutions (i.e. load Testing, performance testing, Infrastructure, Security, SOA & Test Automation) & Senior Test Consulting Strategy. TestLogistics provide top tier organisations with a range of services which enable significant improvements on quality, delivery and overall value.
When building and deploying new security infrastructure, the moment eventually arrives where you have to connect your new system to the Internet. This is the moment of truth, where you expose your carefully crafted infrastructure to hackers, crackers, phishers and script kiddies who are always to exploit someone else’ mistakes.
Before you get to this point, you want to have tested the security of you deployment very carefully, and this often gets overlooked in project planning. Many a project has stalled because the business would not approve connecting an untested build to the Internet, and it was not possible to perform effective testing without having the infrastructure connected to the Internet. Consideration should be given to security testing as early as possible in the design phase of the project: who will do the testing, and what sort of access and connectivity will they need? How can that access and connectivity be provisioned without exposing the new deployment to the Internet at large?
TestLogistics (www.testlogistics.net) recommends that the first phase of security testing be conducted in house, using static testing techniques to ensure that the design and configuration of the new infrastructure complies with the organisation’s security policy, and to establish a working baseline. This work can be started very early in the project, and should ideally be commenced before the detailed design is signed off and before equipment is purchased. Regular review phases will ensure that there is no unapproved “drift” from the baseline.
Melodie Neal (Principal Consultant with TestLogistics, and a Certified Internet Systems Security Professional) recommends that the second phase of security infrastructure testing should be white box style internal testing, conducted from within the network where the new infrastructure resides. In this phase the testers should be given access to the systems either as trusted users, or as attackers who have already breached the defences. The goal in this phase is to uncover vulnerabilities that could be exploited, and to understand the extent of the damage that a successful attack could cause.
External testing should initially be mimicked using a harness to emulate access from the Internet. This type of harness can often be provisioned using a low-end router to provide connectivity for the testers to the “outside” of the infrastructure. Testing in this phase should include a mix of positive and negative testing, to ensure that traffic and transactions that should pass and succeed do so, and that all other traffic is blocked, and that appropriate logging is in place.
Formal penetration testing should always be performed by a third party. A third party is more likely to spot deficiencies that the people who have worked on building the infrastructure. If a third party is engaged to perform internal testing, that work should be completed and the results analysed – and any defects remediated – before external testing proceeds. Both internal and external testing should be re-executed on a regular basis, in line with the organisation’s security policy.
Samuel worked for TestLogistics, TestLogistics is a leading provider of Testing Logistics Solutions (including Test Environments Management, Test Data Management, Harnessing and Test Lab Operations), Technical Testing Solutions (i.e. load Testing, performance testing, Infrastructure, Security, SOA & Test Automation) & Senior Test Consulting Strategy. TestLogistics provide top tier organisations with a range of services which enable significant improvements on quality, delivery and overall value.
When building and deploying new security infrastructure, the moment eventually arrives where you have to connect your new system to the Internet. This is the moment of truth, where you expose your carefully crafted infrastructure to hackers, crackers, phishers and script kiddies who are always to exploit someone else’ mistakes.
Before you get to this point, you want to have tested the security of you deployment very carefully, and this often gets overlooked in project planning. Many a project has stalled because the business would not approve connecting an untested build to the Internet, and it was not possible to perform effective testing without having the infrastructure connected to the Internet. Consideration should be given to security testing as early as possible in the design phase of the project: who will do the testing, and what sort of access and connectivity will they need? How can that access and connectivity be provisioned without exposing the new deployment to the Internet at large?
TestLogistics (www.testlogistics.net) recommends that the first phase of security testing be conducted in house, using static testing techniques to ensure that the design and configuration of the new infrastructure complies with the organisation’s security policy, and to establish a working baseline. This work can be started very early in the project, and should ideally be commenced before the detailed design is signed off and before equipment is purchased. Regular review phases will ensure that there is no unapproved “drift” from the baseline.
Melodie Neal (Principal Consultant with TestLogistics, and a Certified Internet Systems Security Professional) recommends that the second phase of security infrastructure testing should be white box style internal testing, conducted from within the network where the new infrastructure resides. In this phase the testers should be given access to the systems either as trusted users, or as attackers who have already breached the defences. The goal in this phase is to uncover vulnerabilities that could be exploited, and to understand the extent of the damage that a successful attack could cause.
External testing should initially be mimicked using a harness to emulate access from the Internet. This type of harness can often be provisioned using a low-end router to provide connectivity for the testers to the “outside” of the infrastructure. Testing in this phase should include a mix of positive and negative testing, to ensure that traffic and transactions that should pass and succeed do so, and that all other traffic is blocked, and that appropriate logging is in place.
Formal penetration testing should always be performed by a third party. A third party is more likely to spot deficiencies that the people who have worked on building the infrastructure. If a third party is engaged to perform internal testing, that work should be completed and the results analysed – and any defects remediated – before external testing proceeds. Both internal and external testing should be re-executed on a regular basis, in line with the organisation’s security policy.
Performance Testing - Why to invest?
Ideally in a real world Project or Testing Lifecycle, it is essential that Performance Testing is considered an Investment priority, this is valuable from a business and IT perspective. Preferably to ensure the Application, System or Environment under test is:
Fit for purpose – Meets agreed business SLA’s/Performance level requirements.
Responsive – Performance responsiveness is crucial under various user/load scenarios.
Scalable – Meets current and future capacity requirements to scale up or scale out.
Stable – Meets Performance level requirements under load.
Confidence – Business and IT Stakeholders need to be confident the system will perform to expected requirements and SLA’s.
Further to the above, another critical success factor in ascertaining whether you should invest in performance testing is evaluating your Return on Investment (ROI). Some of the elements that can provide justification for this include:
Application Tuning – Find and fix architectural defects and Performance Bottlenecks.
Environment/Infrastructure Tuning – Improved efficiency of existing hardware.
Capacity Planning – Identifying the size and scale for future capacity requirements.
All of the above principles and concepts are considered ‘best practice’ and are advised to be applied in a traditional Performance Testing Model. Clearly time and budget are constraints, but if the investment is available it is certainly worth the while to ensure stability and sustainability to IT Projects longer term.
From our experience, there are a number of areas within a Performance Testing practice or function we can provide a significant value proposition, these include:
Senior Management Expertise – Strong Non-Functional Test Strategy & Management
NFT SME Capability – Providing resources that enhance delivery and provide subject matter expertise (SME) in Performance Testing and tooling.
Performance Engineering – Optimised approach towards Architectural test analysis, Performance tuning with a focus on customer experience.
Static Testing of Non Functional Requirements
Non-functional requirements analysis and traceability
Author Bio :
Samuel worked for TestLogistics, TestLogistics is a leading provider of Testing Logistics Solutions (including Performance Testing Test Environments Management, Test Data Management, Harnessing and Test Lab Operations), Technical Testing Solutions (i.e. Performance Testing, Infrastructure, Security, SOA & Test Automation) & Senior Test Consulting Strategy. TestLogistics provide top tier organisations with a range of services which enable significant improvements on quality, delivery and overall value.
Fit for purpose – Meets agreed business SLA’s/Performance level requirements.
Responsive – Performance responsiveness is crucial under various user/load scenarios.
Scalable – Meets current and future capacity requirements to scale up or scale out.
Stable – Meets Performance level requirements under load.
Confidence – Business and IT Stakeholders need to be confident the system will perform to expected requirements and SLA’s.
Further to the above, another critical success factor in ascertaining whether you should invest in performance testing is evaluating your Return on Investment (ROI). Some of the elements that can provide justification for this include:
Application Tuning – Find and fix architectural defects and Performance Bottlenecks.
Environment/Infrastructure Tuning – Improved efficiency of existing hardware.
Capacity Planning – Identifying the size and scale for future capacity requirements.
All of the above principles and concepts are considered ‘best practice’ and are advised to be applied in a traditional Performance Testing Model. Clearly time and budget are constraints, but if the investment is available it is certainly worth the while to ensure stability and sustainability to IT Projects longer term.
From our experience, there are a number of areas within a Performance Testing practice or function we can provide a significant value proposition, these include:
Senior Management Expertise – Strong Non-Functional Test Strategy & Management
NFT SME Capability – Providing resources that enhance delivery and provide subject matter expertise (SME) in Performance Testing and tooling.
Performance Engineering – Optimised approach towards Architectural test analysis, Performance tuning with a focus on customer experience.
Static Testing of Non Functional Requirements
Non-functional requirements analysis and traceability
Author Bio :
Samuel worked for TestLogistics, TestLogistics is a leading provider of Testing Logistics Solutions (including Performance Testing Test Environments Management, Test Data Management, Harnessing and Test Lab Operations), Technical Testing Solutions (i.e. Performance Testing, Infrastructure, Security, SOA & Test Automation) & Senior Test Consulting Strategy. TestLogistics provide top tier organisations with a range of services which enable significant improvements on quality, delivery and overall value.
Subscribe to:
Posts (Atom)